Method and apparatus for transmitting/receiving broadcasting signal including robust header compression packet stream and fast information

ABSTRACT

A method for transmitting a broadcast signal includes generating a packet carrying a broadcast service and service signaling information, and a packet carrying fast information for supporting rapid service scans and service acquisition, the fast information including identification information for identifying the broadcast service, service category information representing a category of the broadcast service and hidden information representing whether or not the broadcast service is related to a test service; generating a robust header compression (RoHC) packet by compressing a header of each packet, and signaling information including context information generated from the compressing the header of each packet; and transmitting a signal frame including the RoHC packet and the signaling information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of co-pending U.S. patent applicationSer. No. 16/743,542 filed on Jan. 15, 2020, which is a Continuation ofU.S. patent application Ser. No. 14/913,962 filed on Feb. 23, 2016 (nowU.S. Pat. No. 10,582,023 issued on Mar. 3, 2020), which is the NationalPhase of PCT International Application No. PCT/KR2015/000250 filed onJan. 9, 2015, which claims the priority benefit under 35 U.S.C. § 119(e)to U.S. Provisional Application No. 61/927,450 filed on Jan. 14, 2014,all of which are hereby expressly incorporated by reference into thepresent application.

BACKGROUND OF THE INVENTION Field of the Invention

The present invention relates to transmission and reception of abroadcast signal, and more particularly to a method and/or apparatus fortransmitting and receiving a broadcast signal including a robust headercompression (RoHC) packet stream and fast information.

Discussion of the Related Art

According to digital broadcast, a plurality of broadcast services can betransmitted through a specific frequency, unlike analog broadcast. Inaddition, detailed information for reception of a broadcast service canbe changed according to things such as broadcasters. Thus, in order toreceive each broadcast service, a broadcast receiving apparatus needs toperform broadcast service scan for acquisition of connection informationrequired to receive each broadcast service. To this end, the broadcastreceiving apparatus needs to sequentially tune frequencies within abaseband as a frequency band for transmission of a broadcast service, toreceive a broadcast signal, and to acquire service connectioninformation from the received broadcast signal. Thus, a user needs towait for completion of the broadcast service scan in order to watchbroadcast. Accordingly, there has been a need to determine maximum timerequired to complete the broadcast service scan by many broadcasters andto complete the broadcast service scan by a broadcast receivingapparatus within the maximum time by a manufacturer of the broadcastreceiving apparatus.

In general, IP/UDP/RTP header fields can be classified into static,delta, dynamic, and inferred attributes. The static is a field having apredetermined value in one end to end packet stream, corresponds to anIP address and a port number, and also corresponds to a field havingwell known values like in a version field of RTP or IP. The delta is afield having a predetermined difference value from a previous packet andcorresponds to a sequence number, etc. The dynamic is a field that israndomly changed and corresponds to checksum, an ID of an IP packet,etc. The inferred corresponds to a field that can be inferred viaanother header field, etc. like the length field. Concept of contextidentifier (CID) has been introduced as a general header compressionscheme. When a transmitter side (compressor) initially transmits apacket having a full header in a non-compression state, to which aspecific CID is added, and then transmits a next packet with the sameCID, from which header fields having static, delta, or inferredattribute are omitted, a receiver side (decompressor) restores anoverall RTP header by adding fields omitted from a compression headerreceived after a second packet with reference to header fieldinformation that is initially stored based on the CID. In the case ofdelta header, when the compressor and the decompressor store most fieldsof the full header and then the compressor transmits only a differencevalue from a previous packet, the decompressor restores the delta headerby compensating a pre-stored value for the difference value.

A robust header compression (RoHC) scheme classifieds a header fieldinto static, dynamic, and inferable, defines a compression release stateat a compressor as initialization and refresh (IR), first order (FO),and second order (SO), and defines a compression release state at adecompressor as no context (NC), static context (SC), and full context(FC). The RoHC scheme initially begins to perform transmission with alow compression ratio and maintains a state in which the currentcompression ratio reaches a highest compression ratio as possible. Inthis regard, when the decompressor fails in context initialization orcompression release, the compressor state is returned to IR as a lowestcompression step and in this state, the compressor transmits a fullheader. Then, in the FO step, the compressor omits a static field anddoes not lastly transmit all fields that can be compressed in an SOstep. State transition of the decompressor can be moved to SC and FCsteps from NC as a lowest step, and an optimal compression releaseoperation is performed in the FC step.

Robust header compression (RoHC) can be configured for a bidirectionaltransmission system. In the bidirectional transmission system, a RoHCcompressor and a RoHC decompressor can perform an initial set upprocedure and in this procedure, can transmit and receive a parameterrequired for the initial procedure. The procedure for transmitting andreceiving the parameter required for aforementioned initial procedurecan be referred as a negotiation procedure or an initializationprocedure. However, a unidirectional system such as a broadcast systemcannot perform the aforementioned negotiation procedure and needs toreplace the aforementioned initialization procedure with a separatemethod.

SUMMARY OF THE INVENTION

Therefore, the present invention has been made in view of the aboveproblems, and it is an object of the present invention to provide amethod and/or apparatus for transmitting and receiving a broadcastsignal including robust header compression (RoHC) packet stream and fastinformation.

It is an object of the present invention to provide a method forperforming a RoHC initialization procedure in a unidirectionaltransmission system.

It is an object of the present invention to provide a method fortransmitting a parameter required for a RoHC initialization procedure ina unidirectional transmission system.

In addition, it is an object of the present invention to provide amethod for pre-acquiring a parameter required for a RoHC initializationprocedure in a unidirectional transmission system.

In accordance with an aspect of the present invention, the above andother objects can be accomplished by the provision of a method fortransmitting a broadcast signal, the method including encoding broadcastdata, generating a packet including the encoded broadcast data,generating a robust header compression (RoHC) packet by performing RoHCon a header of the generated packet, generating fast informationincluding configuration information of a broadcast stream and broadcastservice related information and transmitting the fast informationthrough a second channel, and transmitting the broadcast streamincluding the generated RoHC packet through a second channel.

The fast information may include RoHC initialization information forinitialization of information about the RoHC.

The RoHC initialization information may include context identificationinformation for identification of context indicating one or more RoHCpacket units, context profile information indicating a range of aprotocol for compression of a header of a RoHC packet, maximum contextidentification information indicating a maximum value of the contextidentification information, and large context identification informationindicating representation format of the context identificationinformation.

The RoHC initialization information may include at least one of feedbackchannel information indicating whether a backward channel fortransmission of feedback information is present in a channel fortransmission of a RoHC packet and maximum segment size informationindicating a maximum size of one segment when a RoHC packet is segmentedto one or more segments.

The RoHC initialization information may be included in a service levelin the fast information.

The fast information may further include component related informationincluded in a broadcast service, and the RoHC initialization informationmay be included in a component level in the fast information.

The RoHC initialization information may be included in a descriptor.

In accordance with another aspect of the present invention, there isprovided a method for receiving a broadcast signal, the method includingreceiving fast information including configuration information of abroadcast stream and broadcast service related information through afirst channel, receiving the broadcast stream including a robust headercompression (RoHC) packet on which RoHC is performed, through a secondchannel, extracting a RoHC packet from the received broadcast streamusing the received fast information and decompressing the extracted RoHCpacket to generate an IP packet, extracting broadcast data from thegenerated IP packet, and decoding the extracted broadcast data.

The fast information may include RoHC initialization information forinitialization of information about the RoHC.

The RoHC initialization information may include context identificationinformation for identification of context indicating one or more RoHCpacket units, context profile information indicating a range of aprotocol for compression of a header of a RoHC packet, maximum contextidentification information indicating a maximum value of the contextidentification information, and large context identification informationindicating representation format of the context identificationinformation.

The RoHC initialization information may include at least one of feedbackchannel information indicating whether a backward channel fortransmission of feedback information is present in a channel fortransmission of a RoHC packet and maximum segment size informationindicating a maximum size of one segment when a RoHC packet is segmentedto one or more segments.

The RoHC initialization information may be included in a service levelin the fast information.

The fast information may further include component related informationincluded in a broadcast service, and the RoHC initialization informationmay be included in a component level in the fast information.

The RoHC initialization information may be included in a descriptor.

In accordance with another aspect of the present invention, there isprovided an apparatus for transmitting a broadcast signal, the apparatusincluding an encoder for encoding broadcast data, a packet generator forgenerating a packet including the encoded broadcast data, a robustheader compression (RoHC) compressor for generating a RoHC packet byperforming RoHC on a header of the generated packet, a first transmitterfor generating fast information including configuration information of abroadcast stream and broadcast service related information andtransmitting the fast information through a first channel, and a secondtransmitter for transmitting the broadcast stream including thegenerated RoHC packet through a second channel.

In accordance with another aspect of the present invention, there isprovided an apparatus for receiving a broadcast signal, the apparatusincluding a first receiver for receiving fast information includingconfiguration information of a broadcast stream and broadcast servicerelated information through a first channel, a second receiver forreceiving the broadcast stream including a robust header compression(RoHC) packet on which RoHC is performed, through a second channel, aRoHC decompressor for extracting a RoHC packet from the receivedbroadcast stream using the received fast information and decompressingthe extracted RoHC packet to generate an IP packet, an extractor forextracting broadcast data from the generated IP packet, and a decoderfor decoding the extracted broadcast data.

Advantageous Effects

According to the present invention, a broadcast signal including arobust header compression (RoHC) packet stream and fast information canbe transmitted and received.

According to the present invention, a RoHC initialization procedure canbe performed in a unidirectional transmission system.

According to the present invention, a parameter required for a RoHCinitialization procedure can be transmitted in a unidirectionaltransmission system.

According to the present invention, a parameter required for a RoHCinitialization procedure can be pre-acquired in a unidirectionaltransmission system.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are included to provide a furtherunderstanding of the invention and are incorporated in and constitute apart of this application, illustrate embodiment(s) of the invention andtogether with the description serve to explain the principle of theinvention. In the drawings:

FIG. 1 illustrates a structure of an apparatus for transmittingbroadcast signals for future broadcast services according to anembodiment of the present invention.

FIG. 2 illustrates an input formatting block according to one embodimentof the present invention.

FIG. 3 illustrates an input formatting block according to anotherembodiment of the present invention.

FIG. 4 illustrates an input formatting block according to anotherembodiment of the present invention.

FIG. 5 illustrates a BICM block according to an embodiment of thepresent invention.

FIG. 6 illustrates a BICM block according to another embodiment of thepresent invention.

FIG. 7 illustrates a frame building block according to one embodiment ofthe present invention.

FIG. 8 illustrates an OFDM generation block according to an embodimentof the present invention.

FIG. 9 illustrates a structure of an apparatus for receiving broadcastsignals for future broadcast services according to an embodiment of thepresent invention.

FIG. 10 illustrates a frame structure according to an embodiment of thepresent invention.

FIG. 11 illustrates a signaling hierarchy structure of the frameaccording to an embodiment of the present invention.

FIG. 12 illustrates preamble signaling data according to an embodimentof the present invention.

FIG. 13 illustrates PLS1 data according to an embodiment of the presentinvention.

FIG. 14 illustrates PLS2 data according to an embodiment of the presentinvention.

FIG. 15 illustrates PLS2 data according to another embodiment of thepresent invention.

FIG. 16 illustrates a logical structure of a frame according to anembodiment of the present invention.

FIG. 17 illustrates PLS mapping according to an embodiment of thepresent invention.

FIG. 18 illustrates EAC mapping according to an embodiment of thepresent invention.

FIG. 19 illustrates FIC mapping according to an embodiment of thepresent invention.

FIG. 20 illustrates a type of DP according to an embodiment of thepresent invention.

FIG. 21 illustrates DP mapping according to an embodiment of the presentinvention.

FIG. 22 illustrates an FEC structure according to an embodiment of thepresent invention.

FIG. 23 illustrates a bit interleaving according to an embodiment of thepresent invention.

FIG. 24 illustrates a cell-word demultiplexing according to anembodiment of the present invention.

FIG. 25 illustrates a time interleaving according to an embodiment ofthe present invention.

FIG. 26 illustrates the basic operation of a twisted row-column blockinterleaver according to an embodiment of the present invention.

FIG. 27 illustrates an operation of a twisted row-column blockinterleaver according to another embodiment of the present invention.

FIG. 28 illustrates a diagonal-wise reading pattern of a twistedrow-column block interleaver according to an embodiment of the presentinvention.

FIG. 29 illustrates interleaved XFECBLOCKs from each interleaving arrayaccording to an embodiment of the present invention.

FIG. 30 is a view illustrating a configuration of a broadcast receptiondevice according to an embodiment of the present invention.

FIG. 31 is a view illustrating a transport layer of broadcast serviceaccording to an embodiment of the present invention.

FIG. 32 is a view illustrating a broadcast transport frame according toan embodiment of the present invention.

FIG. 33 is a view of a broadcast transport frame according to anotherembodiment of the present invention.

FIG. 34 illustrates a syntax of a fast information chunk according to anembodiment of the present invention.

FIG. 35 is a view when a broadcast transmission device transmitsbroadcast service according to an embodiment of the present invention.

FIG. 36 is a view when a broadcast reception device scans broadcastservice according to an embodiment of the present invention.

FIG. 37 illustrates a syntax of a fast information chunk according toanother embodiment of the present invention.

FIG. 38 illustrates a syntax of a fast information chunk according toanother embodiment of the present invention.

FIG. 39 illustrates a syntax of a fast information chunk according toanother embodiment of the present invention.

FIG. 40 illustrates a syntax of a fast information chunk according toanother embodiment of the present invention.

FIG. 41 is a view when a broadcast transmission device transmitsbroadcast service according to another embodiment of the presentinvention.

FIG. 42 is a view when a broadcast reception device scans broadcastservice according to another embodiment of the present invention.

FIG. 43 is a flowchart of broadcast data allowing a broadcast receptiondevice to scan broadcast service according to an embodiment of thepresent invention.

FIG. 44 is a flowchart of broadcast data allowing a broadcast receptiondevice to obtain broadcast service information according to anembodiment of the present invention.

FIG. 45 illustrates a syntax of a fast information table according to anembodiment of the present invention.

FIG. 46 illustrates a syntax of a fast information table according toanother embodiment of the present invention.

FIG. 47 illustrates a syntax of a fast information table according toanother embodiment of the present invention.

FIG. 48 illustrates a syntax of a fast information table according toanother embodiment of the present invention.

FIG. 49 is a diagram illustrating configuration of ROHC_init_descriptor() according to an embodiment of the present invention.

FIG. 50 is a diagram illustrating configuration ofFast_Information_Chunk( ) including ROHC_init_descriptor( ) according toan embodiment of the present invention.

FIG. 51 is a diagram illustrating configuration ofFast_Information_Chunk( ) including a parameter required for a RoHCinitial procedure according to an embodiment of the present invention.

FIG. 52 is a diagram illustrating configuration ofFast_Information_Chunk( ) including ROHC_init_descriptor( ) according toanother embodiment of the present invention.

FIG. 53 is a diagram illustrating configuration ofFast_Information_Chunk( ) including a parameter required for a RoHCinitial procedure according to another embodiment of the presentinvention.

FIG. 54 is a flowchart of a method for transmitting a broadcast signalaccording to an embodiment of the present invention.

FIG. 55 is a flowchart of a method for receiving a broadcast signalaccording to an embodiment of the present invention.

FIG. 56 is a diagram illustrating configuration of a broadcast signaltransmitting apparatus L56060 according to an embodiment of the presentinvention.

FIG. 57 is a diagram illustrating configuration of a broadcast signalreceiving apparatus L57060 according to an embodiment of the presentinvention.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to the preferred embodiments of thepresent invention, examples of which are illustrated in the accompanyingdrawings. The detailed description, which will be given below withreference to the accompanying drawings, is intended to explain exemplaryembodiments of the present invention, rather than to show the onlyembodiments that can be implemented according to the present invention.The following detailed description includes specific details in order toprovide a thorough understanding of the present invention. However, itwill be apparent to those skilled in the art that the present inventionmay be practiced without such specific details.

Although most terms used in the present invention have been selectedfrom general ones widely used in the art, some terms have beenarbitrarily selected by the applicant and their meanings are explainedin detail in the following description as needed. Thus, the presentinvention should be understood based upon the intended meanings of theterms rather than their simple names or meanings.

In this specification, ‘signaling’ indicates transport/reception ofservice information (SI) provided by a broadcasting system, an Internetbroadcasting system, and/or a broadcasting/Internet convergence system.The service information includes broadcasting service information (forexample, ATSC-SI and/or DVB-SI) provided by existing broadcastingsystems.

In this specification, a ‘broadcast signal’ is defined as a conceptincluding a signal and/or data provided in bidirectional broadcasting,such as Internet broadcasting, broadband broadcasting, communicationbroadcasting, data broadcasting, and/or Video On Demand (VOD), inaddition to terrestrial broadcasting, cable broadcasting, satellitebroadcasting, and/or mobile broadcasting.

In this specification, ‘PLP’ means a fixed unit for transporting databelonging to a physical layer. Consequently, an element named ‘PLP’ mayalso be named a ‘data unit’ or a ‘data pipe’.

One of the powerful applications utilized in a digital broadcasting(DTV) service may be a hybrid broadcasting service based on interlockingbetween a broadcasting network and an Internet network. In the hybridbroadcasting service,

enhancement data associated with broadcast audio/video (A/V) contenttransported through a terrestrial broadcasting network or a portion ofthe broadcast A/V content is transported through the Internet network inreal time such that users can experience various kinds of content.

It is an object of the present invention to propose a method ofencapsulating an IP packet, an MPEG-2 TS packet, and a packet that canbe used in other broadcasting system such that the packets can bedelivered to a physical layer in a next generation digital broadcastingsystem. In addition, the present invention also proposes a method oftransporting layer 2 signaling with the same header format.

The following procedures may be realized by an apparatus. For example, asignaling processing unit, a protocol processing unit, a processor,and/or a packet generation unit may perform the following procedures.

The present invention provides apparatuses and methods for transmittingand receiving broadcast signals for future broadcast services. Futurebroadcast services according to an embodiment of the present inventioninclude a terrestrial broadcast service, a mobile broadcast service, aUHDTV service, etc.

The apparatuses and methods for transmitting according to an embodimentof the present invention may be categorized into a base profile for theterrestrial broadcast service, a handheld profile for the mobilebroadcast service and an advanced profile for the UHDTV service. In thiscase, the base profile can be used as a profile for both the terrestrialbroadcast service and the mobile broadcast service. That is, the baseprofile can be used to define a concept of a profile which includes themobile profile. This can be changed according to intention of thedesigner.

The present invention may process broadcast signals for the futurebroadcast services through non-MIMO (Multiple Input Multiple Output) orMIMO according to one embodiment. A non-MIMO scheme according to anembodiment of the present invention may include a MISO (Multiple InputSingle Output) scheme, a SISO (Single Input Single Output) scheme, etc.

While MISO or MIMO uses two antennas in the following for convenience ofdescription, the present invention is applicable to systems using two ormore antennas.

The present invention may define three physical layer (PL) profiles(base, handheld and advanced profiles) each optimized to minimizereceiver complexity while attaining the performance required for aparticular use case. The physical layer (PHY) profiles are subsets ofall configurations that a corresponding receiver should implement.

The three PHY profiles share most of the functional blocks but differslightly in specific blocks and/or parameters. Additional PHY profilescan be defined in the future. For the system evolution, future profilescan also be multiplexed with the existing profiles in a single RFchannel through a future extension frame (FEF). The details of each PHYprofile are described below.

1. Base Profile

The base profile represents a main use case for fixed receiving devicesthat are usually connected to a roof-top antenna. The base profile alsoincludes portable devices that could be transported to a place butbelong to a relatively stationary reception category. Use of the baseprofile could be extended to handheld devices or even vehicular by someimproved implementations, but those use cases are not expected for thebase profile receiver operation.

Target SNR range of reception is from approximately 10 to 20 dB, whichincludes the 15 dB SNR reception capability of the existing broadcastsystem (e.g. ATSC A/53). The receiver complexity and power consumptionis not as critical as in the battery-operated handheld devices, whichwill use the handheld profile. Key system parameters for the baseprofile are listed in below table 1.

TABLE 1 LDPC codeword length 16K, 64K bits Constellation size 4~10 bpcu(bits per channel use) Time de-interleaving memory size ≤2¹⁹ data cellsPilot patterns Pilot pattern for fixed reception FFT size 16K, 32Kpoints

2. Handheld Profile

The handheld profile is designed for use in handheld and vehiculardevices that operate with battery power. The devices can be moving withpedestrian or vehicle speed. The power consumption as well as thereceiver complexity is very important for the implementation of thedevices of the handheld profile. The target SNR range of the handheldprofile is approximately 0 to 10 dB, but can be configured to reachbelow 0 dB when intended for deeper indoor reception.

In addition to low SNR capability, resilience to the Doppler Effectcaused by receiver mobility is the most important performance attributeof the handheld profile. Key system parameters for the handheld profileare listed in the below table 2.

TABLE 2 LDPC codeword length 16K bits Constellation size 2~8 bpcu Timede-interleaving memory size ≤2¹⁸ data cells Pilot patterns Pilotpatterns for mobile and indoor reception FFT size 8K, 16K points

3. Advanced Profile

The advanced profile provides highest channel capacity at the cost ofmore implementation complexity. This profile requires using MIMOtransmission and reception, and UHDTV service is a target use case forwhich this profile is specifically designed. The increased capacity canalso be used to allow an increased number of services in a givenbandwidth, e.g., multiple SDTV or HDTV services.

The target SNR range of the advanced profile is approximately 20 to 30dB. MIMO transmission may initially use existing elliptically-polarizedtransmission equipment, with extension to full-power cross-polarizedtransmission in the future. Key system parameters for the advancedprofile are listed in below table 3.

TABLE 3 LDPC codeword length 16K, 64K bits Constellation size 8~12 bpcuTime de-interleaving memory size ≤2¹⁹ data cells Pilot patterns Pilotpattern for fixed reception FFT size 16K, 32K points

In this case, the base profile can be used as a profile for both theterrestrial broadcast service and the mobile broadcast service. That is,the base profile can be used to define a concept of a profile whichincludes the mobile profile. Also, the advanced profile can be dividedadvanced profile for a base profile with MIMO and advanced profile for ahandheld profile with MIMO. Moreover, the three profiles can be changedaccording to intention of the designer.

The following terms and definitions may apply to the present invention.The following terms and definitions can be changed according to design.

auxiliary stream: sequence of cells carrying data of as yet undefinedmodulation and coding, which may be used for future extensions or asrequired by broadcasters or network operators.

base data pipe: data pipe that carries service signaling data.

baseband frame (or BBFRAME): set of Kbch bits which form the input toone FEC encoding process (BCH and LDPC encoding).

cell: modulation value that is carried by one carrier of the OFDMtransmission.

coded block: LDPC-encoded block of PLS1 data or one of the LDPC-encodedblocks of PLS2 data.

data pipe: logical channel in the physical layer that carries servicedata or related metadata, which may carry one or multiple service(s) orservice component(s).

data pipe unit: a basic unit for allocating data cells to a DP in aframe.

data symbol: OFDM symbol in a frame which is not a preamble symbol (theframe signaling symbol and frame edge symbol is included in the datasymbol).

DP_ID: this 8 bit field identifies uniquely a DP within the systemidentified by the SYSTEM_ID.

dummy cell: cell carrying a pseudorandom value used to fill theremaining capacity not used for PLS signaling, DPs or auxiliary streams.

emergency alert channel: part of a frame that carries EAS informationdata.

frame: physical layer time slot that starts with a preamble and endswith a frame edge symbol.

frame repetition unit: a set of frames belonging to same or differentphysical layer profile including a FEF, which is repeated eight times ina super-frame.

fast information channel: a logical channel in a frame that carries themapping information between a service and the corresponding base DP.

FECBLOCK: set of LDPC-encoded bits of a DP data.

FFT size: nominal FFT size used for a particular mode, equal to theactive symbol period Ts expressed in cycles of the elementary period T.

frame signaling symbol: OFDM symbol with higher pilot density used atthe start of a frame in certain combinations of FFT size, guard intervaland scattered pilot pattern, which carries a part of the PLS data.

frame edge symbol: OFDM symbol with higher pilot density used at the endof a frame in certain combinations of FFT size, guard interval andscattered pilot pattern.

frame-group: the set of all the frames having the same PHY profile typein a super-frame.

future extension frame: physical layer time slot within the super-framethat could be used for future extension, which starts with a preamble.

Futurecast UTB system: proposed physical layer broadcasting system, ofwhich the input is one or more MPEG2-TS or IP or general stream(s) andof which the output is an RF signal.

input stream: A stream of data for an ensemble of services delivered tothe end users by the system.

normal data symbol: data symbol excluding the frame signaling symbol andthe frame edge symbol.

PHY profile: subset of all configurations that a corresponding receivershould implement.

PLS: physical layer signaling data consisting of PLS1 and PLS2.

PLS1: a first set of PLS data carried in the FSS symbols having a fixedsize, coding and modulation, which carries basic information about thesystem as well as the parameters needed to decode the PLS2.

NOTE: PLS1 data remains constant for the duration of a frame-group.

PLS2: a second set of PLS data transmitted in the FSS symbol, whichcarries more detailed PLS data about the system and the DPs.

PLS2 dynamic data: PLS2 data that may dynamically change frame-by-frame.

PLS2 static data: PLS2 data that remains static for the duration of aframe-group.

preamble signaling data: signaling data carried by the preamble symboland used to identify the basic mode of the system.

preamble symbol: fixed-length pilot symbol that carries basic PLS dataand is located in the beginning of a frame.

NOTE: The preamble symbol is mainly used for fast initial band scan todetect the system signal, its timing, frequency offset, and FFTsize.

reserved for future use: not defined by the present document but may bedefined in future.

superframe: set of eight frame repetition units.

time interleaving block (TI block): set of cells within which timeinterleaving is carried out, corresponding to one use of the timeinterleaver memory.

TI group: unit over which dynamic capacity allocation for a particularDP is carried out, made up of an integer, dynamically varying number ofXFECBLOCKs.

NOTE: The TI group may be mapped directly to one frame or may be mappedto multiple frames. It may contain one or more TI blocks.

Type 1 DP: DP of a frame where all DPs are mapped into the frame in TDMfashion.

Type 2 DP: DP of a frame where all DPs are mapped into the frame in FDMfashion.

XFECBLOCK: set of Ncells cells carrying all the bits of one LDPCFECBLOCK.

FIG. 1 illustrates a structure of an apparatus for transmittingbroadcast signals for future broadcast services according to anembodiment of the present invention.

The apparatus for transmitting broadcast signals for future broadcastservices according to an embodiment of the present invention can includean input formatting block 1000, a BICM (Bit interleaved coding &modulation) block 1010, a frame structure block 1020, an OFDM(Orthogonal Frequency Division Multiplexing) generation block 1030 and asignaling generation block 1040. A description will be given of theoperation of each module of the apparatus for transmitting broadcastsignals.

IP stream/packets and MPEG2-TS are the main input formats, other streamtypes are handled as General Streams. In addition to these data inputs,Management Information is input to control the scheduling and allocationof the corresponding bandwidth for each input stream. One or multiple TSstream(s), IP stream(s) and/or General Stream(s) inputs aresimultaneously allowed.

The input formatting block 1000 can demultiplex each input stream intoone or multiple data pipe(s), to each of which an independent coding andmodulation is applied. The data pipe (DP) is the basic unit forrobustness control, thereby affecting quality-of-service (QoS). One ormultiple service(s) or service component(s) can be carried by a singleDP. Details of operations of the input formatting block 1000 will bedescribed later.

The data pipe is a logical channel in the physical layer that carriesservice data or related metadata, which may carry one or multipleservice(s) or service component(s).

Also, the data pipe unit: a basic unit for allocating data cells to a DPin a frame.

In the BICM block 1010, parity data is added for error correction andthe encoded bit streams are mapped to complex-value constellationsymbols. The symbols are interleaved across a specific interleavingdepth that is used for the corresponding DP. For the advanced profile,MIMO encoding is performed in the BICM block 1010 and the additionaldata path is added at the output for MIMO transmission. Details ofoperations of the BICM block 1010 will be described later.

The Frame Building block 1020 can map the data cells of the input DPsinto the OFDM symbols within a frame. After mapping, the frequencyinterleaving is used for frequency-domain diversity, especially tocombat frequency-selective fading channels. Details of operations of theFrame Building block 1020 will be described later.

After inserting a preamble at the beginning of each frame, the OFDMGeneration block 1030 can apply conventional OFDM modulation having acyclic prefix as guard interval. For antenna space diversity, adistributed MISO scheme is applied across the transmitters. In addition,a Peak-to-Average Power Reduction (PAPR) scheme is performed in the timedomain. For flexible network planning, this proposal provides a set ofvarious FFT sizes, guard interval lengths and corresponding pilotpatterns. Details of operations of the OFDM Generation block 1030 willbe described later.

The Signaling Generation block 1040 can create physical layer signalinginformation used for the operation of each functional block. Thissignaling information is also transmitted so that the services ofinterest are properly recovered at the receiver side. Details ofoperations of the Signaling Generation block 1040 will be describedlater.

FIGS. 2, 3 and 4 illustrate the input formatting block 1000 according toembodiments of the present invention. A description will be given ofeach figure.

FIG. 2 illustrates an input formatting block according to one embodimentof the present invention. FIG. 2 shows an input formatting module whenthe input signal is a single input stream.

The input formatting block illustrated in FIG. 2 corresponds to anembodiment of the input formatting block 1000 described with referenceto FIG. 1.

The input to the physical layer may be composed of one or multiple datastreams. Each data stream is carried by one DP. The mode adaptationmodules slice the incoming data stream into data fields of the basebandframe (BBF). The system supports three types of input data streams:MPEG2-TS, Internet protocol (IP) and Generic stream (GS). MPEG2-TS ischaracterized by fixed length (188 byte) packets with the first bytebeing a sync-byte (0x47). An IP stream is composed of variable length IPdatagram packets, as signaled within IP packet headers. The systemsupports both IPv4 and IPv6 for the IP stream. GS may be composed ofvariable length packets or constant length packets, signaled withinencapsulation packet headers.

(a) shows a mode adaptation block 2000 and a stream adaptation 2010 forsignal DP and (b) shows a PLS generation block 2020 and a PLS scrambler2030 for generating and processing PLS data. A description will be givenof the operation of each block.

The Input Stream Splitter splits the input TS, IP, GS streams intomultiple service or service component (audio, video, etc.) streams. Themode adaptation module 2010 is comprised of a CRC Encoder, BB (baseband)Frame Slicer, and BB Frame Header Insertion block.

The CRC Encoder provides three kinds of CRC encoding for error detectionat the user packet (UP) level, i.e., CRC-8, CRC-16, and CRC-32. Thecomputed CRC bytes are appended after the UP. CRC-8 is used for TSstream and CRC-32 for IP stream. If the GS stream doesn't provide theCRC encoding, the proposed CRC encoding should be applied.

BB Frame Slicer maps the input into an internal logical-bit format. Thefirst received bit is defined to be the MSB. The BB Frame Slicerallocates a number of input bits equal to the available data fieldcapacity. To allocate a number of input bits equal to the BBF payload,the UP packet stream is sliced to fit the data field of BBF.

BB Frame Header Insertion block can insert fixed length BBF header of 2bytes is inserted in front of the BB Frame. The BBF header is composedof STUFFI (1 bit), SYNCD (13 bits), and RFU (2 bits). In addition to thefixed 2-Byte BBF header, BBF can have an extension field (1 or 3 bytes)at the end of the 2-byte BBF header.

The stream adaptation 2010 is comprised of stuffing insertion block andBB scrambler.

The stuffing insertion block can insert stuffing field into a payload ofa BB frame. If the input data to the stream adaptation is sufficient tofill a BB-Frame, STUFFI is set to ‘0’ and the BBF has no stuffing field.Otherwise STUFFI is set to ‘1’ and the stuffing field is insertedimmediately after the BBF header. The stuffing field comprises two bytesof the stuffing field header and a variable size of stuffing data.

The BB scrambler scrambles complete BBF for energy dispersal. Thescrambling sequence is synchronous with the BBF. The scrambling sequenceis generated by the feed-back shift register.

The PLS generation block 2020 can generate physical layer signaling(PLS) data. The PLS provides the receiver with a means to accessphysical layer DPs. The PLS data consists of PLS1 data and PLS2 data.

The PLS1 data is a first set of PLS data carried in the FSS symbols inthe frame having a fixed size, coding and modulation, which carriesbasic information about the system as well as the parameters needed todecode the PLS2 data. The PLS1 data provides basic transmissionparameters including parameters required to enable the reception anddecoding of the PLS2 data. Also, the PLS1 data remains constant for theduration of a frame-group.

The PLS2 data is a second set of PLS data transmitted in the FSS symbol,which carries more detailed PLS data about the system and the DPs. ThePLS2 contains parameters that provide sufficient information for thereceiver to decode the desired DP. The PLS2 signaling further consistsof two types of parameters, PLS2 Static data (PLS2-STAT data) and PLS2dynamic data (PLS2-DYN data). The PLS2 Static data is PLS2 data thatremains static for the duration of a frame-group and the PLS2 dynamicdata is PLS2 data that may dynamically change frame-by-frame.

Details of the PLS data will be described later.

The PLS scrambler 2030 can scramble the generated PLS data for energydispersal.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 3 illustrates an input formatting block according to anotherembodiment of the present invention.

The input formatting block illustrated in FIG. 3 corresponds to anembodiment of the input formatting block 1000 described with referenceto FIG. 1.

FIG. 3 shows a mode adaptation block of the input formatting block whenthe input signal corresponds to multiple input streams.

The mode adaptation block of the input formatting block for processingthe multiple input streams can independently process the multiple inputstreams.

Referring to FIG. 3, the mode adaptation block for respectivelyprocessing the multiple input streams can include an input streamsplitter 3000, an input stream synchronizer 3010, a compensating delayblock 3020, a null packet deletion block 3030, a head compression block3040, a CRC encoder 3050, a BB frame slicer 3060 and a BB headerinsertion block 3070. Description will be given of each block of themode adaptation block.

Operations of the CRC encoder 3050, BB frame slicer 3060 and BB headerinsertion block 3070 correspond to those of the CRC encoder, BB frameslicer and BB header insertion block described with reference to FIG. 2and thus description thereof is omitted.

The input stream splitter 3000 can split the input TS, IP, GS streamsinto multiple service or service component (audio, video, etc.) streams.

The input stream synchronizer 3010 may be referred as ISSY. The ISSY canprovide suitable means to guarantee Constant Bit Rate (CBR) and constantend-to-end transmission delay for any input data format. The ISSY isalways used for the case of multiple DPs carrying TS, and optionallyused for multiple DPs carrying GS streams.

The compensating delay block 3020 can delay the split TS packet streamfollowing the insertion of ISSY information to allow a TS packetrecombining mechanism without requiring additional memory in thereceiver.

The null packet deletion block 3030, is used only for the TS inputstream case. Some TS input streams or split TS streams may have a largenumber of null-packets present in order to accommodate VBR (variablebit-rate) services in a CBR TS stream. In this case, in order to avoidunnecessary transmission overhead, null-packets can be identified andnot transmitted. In the receiver, removed null-packets can bere-inserted in the exact place where they were originally by referenceto a deleted null-packet (DNP) counter that is inserted in thetransmission, thus guaranteeing constant bit-rate and avoiding the needfor time-stamp (PCR) updating.

The head compression block 3040 can provide packet header compression toincrease transmission efficiency for TS or IP input streams. Because thereceiver can have a priori information on certain parts of the header,this known information can be deleted in the transmitter.

For Transport Stream, the receiver has a-priori information about thesync-byte configuration (0x47) and the packet length (188 Byte). If theinput TS stream carries content that has only one PID, i.e., for onlyone service component (video, audio, etc.) or service sub-component (SVCbase layer, SVC enhancement layer, MVC base view or MVC dependentviews), TS packet header compression can be applied (optionally) to theTransport Stream. IP packet header compression is used optionally if theinput steam is an IP stream.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 4 illustrates an input formatting block according to anotherembodiment of the present invention.

The input formatting block illustrated in FIG. 4 corresponds to anembodiment of the input formatting block 1000 described with referenceto FIG. 1.

FIG. 4 illustrates a stream adaptation block of the input formattingmodule when the input signal corresponds to multiple input streams.

Referring to FIG. 4, the mode adaptation block for respectivelyprocessing the multiple input streams can include a scheduler 4000, a1-Frame delay block 4010, a stuffing insertion block 4020, an in-bandsignaling 4030, a BB Frame scrambler 4040, a PLS generation block 4050and a PLS scrambler 4060. Description will be given of each block of thestream adaptation block.

Operations of the stuffing insertion block 4020, the BB Frame scrambler4040, the PLS generation block 4050 and the PLS scrambler 4060correspond to those of the stuffing insertion block, BB scrambler, PLSgeneration block and the PLS scrambler described with reference to FIG.2 and thus description thereof is omitted.

The scheduler 4000 can determine the overall cell allocation across theentire frame from the amount of FECBLOCKs of each DP. Including theallocation for PLS, EAC and FIC, the scheduler generates the values ofPLS2-DYN data, which is transmitted as in-band signaling or PLS cell inFSS of the frame. Details of FECBLOCK, EAC and FIC will be describedlater.

The 1-Frame delay block 4010 can delay the input data by onetransmission frame such that scheduling information about the next framecan be transmitted through the current frame for in-band signalinginformation to be inserted into the DPs.

The in-band signaling 4030 can insert un-delayed part of the PLS2 datainto a DP of a frame.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 5 illustrates a BICM block according to an embodiment of thepresent invention.

The BICM block illustrated in FIG. 5 corresponds to an embodiment of theBICM block 1010 described with reference to FIG. 1.

As described above, the apparatus for transmitting broadcast signals forfuture broadcast services according to an embodiment of the presentinvention can provide a terrestrial broadcast service, mobile broadcastservice, UHDTV service, etc.

Since QoS (quality of service) depends on characteristics of a serviceprovided by the apparatus for transmitting broadcast signals for futurebroadcast services according to an embodiment of the present invention,data corresponding to respective services needs to be processed throughdifferent schemes. Accordingly, the a BICM block according to anembodiment of the present invention can independently process DPs inputthereto by independently applying SISO, MISO and MIMO schemes to thedata pipes respectively corresponding to data paths. Consequently, theapparatus for transmitting broadcast signals for future broadcastservices according to an embodiment of the present invention can controlQoS for each service or service component transmitted through each DP.

(a) shows the BICM block shared by the base profile and the handheldprofile and (b) shows the BICM block of the advanced profile.

The BICM block shared by the base profile and the handheld profile andthe BICM block of the advanced profile can include plural processingblocks for processing each DP.

A description will be given of each processing block of the BICM blockfor the base profile and the handheld profile and the BICM block for theadvanced profile.

A processing block 5000 of the BICM block for the base profile and thehandheld profile can include a Data FEC encoder 5010, a bit interleaver5020, a constellation mapper 5030, an SSD (Signal Space Diversity)encoding block 5040 and a time interleaver 5050.

The Data FEC encoder 5010 can perform the FEC encoding on the input BBFto generate FECBLOCK procedure using outer coding (BCH), and innercoding (LDPC). The outer coding (BCH) is optional coding method. Detailsof operations of the Data FEC encoder 5010 will be described later.

The bit interleaver 5020 can interleave outputs of the Data FEC encoder5010 to achieve optimized performance with combination of the LDPC codesand modulation scheme while providing an efficiently implementablestructure. Details of operations of the bit interleaver 5020 will bedescribed later.

The constellation mapper 5030 can modulate each cell word from the bitinterleaver 5020 in the base and the handheld profiles, or cell wordfrom the Cell-word demultiplexer 5010-1 in the advanced profile usingeither QPSK, QAM-16, non-uniform QAM (NUQ-64, NUQ-256, NUQ-1024) ornon-uniform constellation (NUC-16, NUC-64, NUC-256, NUC-1024) to give apower-normalized constellation point, el. This constellation mapping isapplied only for DPs. Observe that QAM-16 and NUQs are square shaped,while NUCs have arbitrary shape. When each constellation is rotated byany multiple of 90 degrees, the rotated constellation exactly overlapswith its original one. This “rotation-sense” symmetric property makesthe capacities and the average powers of the real and imaginarycomponents equal to each other. Both NUQs and NUCs are definedspecifically for each code rate and the particular one used is signaledby the parameter DP MOD filed in PLS2 data.

The SSD encoding block 5040 can precode cells in two (2D), three (3D),and four (4D) dimensions to increase the reception robustness underdifficult fading conditions.

The time interleaver 5050 can operates at the DP level. The parametersof time interleaving (TI) may be set differently for each DP. Details ofoperations of the time interleaver 5050 will be described later.

A processing block 5000-1 of the BICM block for the advanced profile caninclude the Data FEC encoder, bit interleaver, constellation mapper, andtime interleaver. However, the processing block 5000-1 is distinguishedfrom the processing block 5000 further includes a cell-worddemultiplexer 5010-1 and a MIMO encoding block 5020-1.

Also, the operations of the Data FEC encoder, bit interleaver,constellation mapper, and time interleaver in the processing block5000-1 correspond to those of the Data FEC encoder 5010, bit interleaver5020, constellation mapper 5030, and time interleaver 5050 described andthus description thereof is omitted.

The cell-word demultiplexer 5010-1 is used for the DP of the advancedprofile to divide the single cell-word stream into dual cell-wordstreams for MIMO processing. Details of operations of the cell-worddemultiplexer 5010-1 will be described later.

The MIMO encoding block 5020-1 can processing the output of thecell-word demultiplexer 5010-1 using MIMO encoding scheme. The MIMOencoding scheme was optimized for broadcasting signal transmission. TheMIMO technology is a promising way to get a capacity increase but itdepends on channel characteristics. Especially for broadcasting, thestrong LOS component of the channel or a difference in the receivedsignal power between two antennas caused by different signal propagationcharacteristics makes it difficult to get capacity gain from MIMO. Theproposed MIMO encoding scheme overcomes this problem using arotation-based pre-coding and phase randomization of one of the MIMOoutput signals.

MIMO encoding is intended for a 2×2 MIMO system requiring at least twoantennas at both the transmitter and the receiver. Two MIMO encodingmodes are defined in this proposal; full-rate spatial multiplexing(FR-SM) and full-rate full-diversity spatial multiplexing (FRFD-SM). TheFR-SM encoding provides capacity increase with relatively smallcomplexity increase at the receiver side while the FRFD-SM encodingprovides capacity increase and additional diversity gain with a greatcomplexity increase at the receiver side. The proposed MIMO encodingscheme has no restriction on the antenna polarity configuration.

MIMO processing is required for the advanced profile frame, which meansall DPs in the advanced profile frame are processed by the MIMO encoder.MIMO processing is applied at DP level. Pairs of the ConstellationMapper outputs NUQ (e1,i and e2,i) are fed to the input of the MIMOEncoder. Paired MIMO Encoder output (g1,i and g2,i) is transmitted bythe same carrier k and OFDM symbol 1 of their respective TX antennas.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 6 illustrates a BICM block according to another embodiment of thepresent invention.

The BICM block illustrated in FIG. 6 corresponds to an embodiment of theBICM block 1010 described with reference to FIG. 1.

FIG. 6 illustrates a BICM block for protection of physical layersignaling (PLS), emergency alert channel (EAC) and fast informationchannel (FIC). EAC is a part of a frame that carries EAS informationdata and FIC is a logical channel in a frame that carries the mappinginformation between a service and the corresponding base DP. Details ofthe EAC and FIC will be described later.

Referring to FIG. 6, the BICM block for protection of PLS, EAC and FICcan include a PLS FEC encoder 6000, a bit interleaver 6010 and aconstellation mapper 6020.

Also, the PLS FEC encoder 6000 can include a scrambler, BCHencoding/zero insertion block, LDPC encoding block and LDPC paritypunturing block. Description will be given of each block of the BICMblock.

The PLS FEC encoder 6000 can encode the scrambled PLS 1/2 data, EAC andFIC section.

The scrambler can scramble PLS1 data and PLS2 data before BCH encodingand shortened and punctured LDPC encoding.

The BCH encoding/zero insertion block can perform outer encoding on thescrambled PLS 1/2 data using the shortened BCH code for PLS protectionand insert zero bits after the BCH encoding. For PLS1 data only, theoutput bits of the zero insertion may be permutted before LDPC encoding.

The LDPC encoding block can encode the output of the BCH encoding/zeroinsertion block using LDPC code. To generate a complete coded block,Cldpc, parity bits, Pldpc are encoded systematically from eachzero-inserted PLS information block, Ildpc and appended after it.

C _(ldpc)[[I _(ldpc) P _(ldpc)]=i ₀ ,i ₁ , . . . ,i _(K) _(ldpc) ₋₁ ,p ₀,p ₁ , . . . ,p _(N) _(ldpc) _(-K) _(ldpc) ₋₁]  [Math FIG. 1]

The LDPC code parameters for PLS1 and PLS2 are as following table 4.

TABLE 4 Signaling K_(ldpc) Type K_(sig) K_(bch) N_(bch)_parity(=N_(bch)) N_(ldpc) N_(ldpc)_parity code rate Q_(ldpc) PLS1 342 1020 601080 4320 3240  1/4 36 PLS2 <1021 >1020 2100 2160 7200 5040 3/10 56

The LDPC parity puncturing block can perform puncturing on the PLS1 dataand PLS 2 data.

When shortening is applied to the PLS1 data protection, some LDPC paritybits are punctured after LDPC encoding. Also, for the PLS2 dataprotection, the LDPC parity bits of PLS2 are punctured after LDPCencoding. These punctured bits are not transmitted.

The bit interleaver 6010 can interleave the each shortened and puncturedPLS1 data and PLS2 data.

The constellation mapper 6020 can map the bit interleaved PLS1 data andPLS2 data onto constellations.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 7 illustrates a frame building block according to one embodiment ofthe present invention.

The frame building block illustrated in FIG. 7 corresponds to anembodiment of the frame building block 1020 described with reference toFIG. 1.

Referring to FIG. 7, the frame building block can include a delaycompensation block 7000, a cell mapper 7010 and a frequency interleaver7020. Description will be given of each block of the frame buildingblock.

The delay compensation block 7000 can adjust the timing between the datapipes and the corresponding PLS data to ensure that they are co-timed atthe transmitter end. The PLS data is delayed by the same amount as datapipes are by addressing the delays of data pipes caused by the InputFormatting block and BICM block. The delay of the BICM block is mainlydue to the time interleaver. In-band signaling data carries informationof the next TI group so that they are carried one frame ahead of the DPsto be signaled. The Delay Compensating block delays in-band signalingdata accordingly.

The cell mapper 7010 can map PLS, EAC, FIC, DPs, auxiliary streams anddummy cells into the active carriers of the OFDM symbols in the frame.The basic function of the cell mapper 7010 is to map data cells producedby the TIs for each of the DPs, PLS cells, and EAC/FIC cells, if any,into arrays of active OFDM cells corresponding to each of the OFDMsymbols within a frame. Service signaling data (such as PSI (programspecific information)/SI) can be separately gathered and sent by a datapipe. The Cell Mapper operates according to the dynamic informationproduced by the scheduler and the configuration of the frame structure.Details of the frame will be described later.

The frequency interleaver 7020 can randomly interleave data cellsreceived from the cell mapper 7010 to provide frequency diversity. Also,the frequency interleaver 7020 can operate on very OFDM symbol paircomprised of two sequential OFDM symbols using a differentinterleaving-seed order to get maximum interleaving gain in a singleframe. Details of operations of the frequency interleaver 7020 will bedescribed later.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions.

FIG. 8 illustrates an OFDM generation block according to an embodimentof the present invention.

The OFDM generation block illustrated in FIG. 8 corresponds to anembodiment of the OFDM generation block 1030 described with reference toFIG. 1.

The OFDM generation block modulates the OFDM carriers by the cellsproduced by the Frame Building block, inserts the pilots, and producesthe time domain signal for transmission. Also, this block subsequentlyinserts guard intervals, and applies PAPR (Peak-to-Average Power Radio)reduction processing to produce the final RF signal.

Referring to FIG. 8, the frame building block can include a pilot andreserved tone insertion block 8000, a 2D-eSFN encoding block 8010, anIFFT (Inverse Fast Fourier Transform) block 8020, a PAPR reduction block8030, a guard interval insertion block 8040, a preamble insertion block8050, other system insertion block 8060 and a DAC block 8070.Description will be given of each block of the frame building block.

The pilot and reserved tone insertion block 8000 can insert pilots andthe reserved tone.

Various cells within the OFDM symbol are modulated with referenceinformation, known as pilots, which have transmitted values known apriori in the receiver. The information of pilot cells is made up ofscattered pilots, continual pilots, edge pilots, FSS (frame signalingsymbol) pilots and FES (frame edge symbol) pilots. Each pilot istransmitted at a particular boosted power level according to pilot typeand pilot pattern. The value of the pilot information is derived from areference sequence, which is a series of values, one for eachtransmitted carrier on any given symbol. The pilots can be used forframe synchronization, frequency synchronization, time synchronization,channel estimation, and transmission mode identification, and also canbe used to follow the phase noise.

Reference information, taken from the reference sequence, is transmittedin scattered pilot cells in every symbol except the preamble, FSS andFES of the frame. Continual pilots are inserted in every symbol of theframe. The number and location of continual pilots depends on both theFFT size and the scattered pilot pattern. The edge carriers are edgepilots in every symbol except for the preamble symbol. They are insertedin order to allow frequency interpolation up to the edge of thespectrum. FSS pilots are inserted in FSS(s) and FES pilots are insertedin FES. They are inserted in order to allow time interpolation up to theedge of the frame.

The system according to an embodiment of the present invention supportsthe SFN network, where distributed MISO scheme is optionally used tosupport very robust transmission mode. The 2D-eSFN is a distributed MISOscheme that uses multiple TX antennas, each of which is located in thedifferent transmitter site in the SFN network.

The 2D-eSFN encoding block 8010 can process a 2D-eSFN processing todistorts the phase of the signals transmitted from multipletransmitters, in order to create both time and frequency diversity inthe SFN configuration. Hence, burst errors due to low flat fading ordeep-fading for a long time can be mitigated.

The IFFT block 8020 can modulate the output from the 2D-eSFN encodingblock 8010 using OFDM modulation scheme. Any cell in the data symbolswhich has not been designated as a pilot (or as a reserved tone) carriesone of the data cells from the frequency interleaver. The cells aremapped to OFDM carriers.

The PAPR reduction block 8030 can perform a PAPR reduction on inputsignal using various PAPR reduction algorithm in the time domain.

The guard interval insertion block 8040 can insert guard intervals andthe preamble insertion block 8050 can insert preamble in front of thesignal. Details of a structure of the preamble will be described later.The other system insertion block 8060 can multiplex signals of aplurality of broadcast transmission/reception systems in the time domainsuch that data of two or more different broadcast transmission/receptionsystems providing broadcast services can be simultaneously transmittedin the same RF signal bandwidth. In this case, the two or more differentbroadcast transmission/reception systems refer to systems providingdifferent broadcast services. The different broadcast services may referto a terrestrial broadcast service, mobile broadcast service, etc. Datarelated to respective broadcast services can be transmitted throughdifferent frames.

The DAC block 8070 can convert an input digital signal into an analogsignal and output the analog signal. The signal output from the DACblock 7800 can be transmitted through multiple output antennas accordingto the physical layer profiles. A Tx antenna according to an embodimentof the present invention can have vertical or horizontal polarity.

The above-described blocks may be omitted or replaced by blocks havingsimilar or identical functions according to design.

FIG. 9 illustrates a structure of an apparatus for receiving broadcastsignals for future broadcast services according to an embodiment of thepresent invention.

The apparatus for receiving broadcast signals for future broadcastservices according to an embodiment of the present invention cancorrespond to the apparatus for transmitting broadcast signals forfuture broadcast services, described with reference to FIG. 1.

The apparatus for receiving broadcast signals for future broadcastservices according to an embodiment of the present invention can includea synchronization & demodulation module 9000, a frame parsing module9010, a demapping & decoding module 9020, an output processor 9030 and asignaling decoding module 9040. A description will be given of operationof each module of the apparatus for receiving broadcast signals.

The synchronization & demodulation module 9000 can receive input signalsthrough m Rx antennas, perform signal detection and synchronization withrespect to a system corresponding to the apparatus for receivingbroadcast signals and carry out demodulation corresponding to a reverseprocedure of the procedure performed by the apparatus for transmittingbroadcast signals.

The frame parsing module 9100 can parse input signal frames and extractdata through which a service selected by a user is transmitted. If theapparatus for transmitting broadcast signals performs interleaving, theframe parsing module 9100 can carry out deinterleaving corresponding toa reverse procedure of interleaving. In this case, the positions of asignal and data that need to be extracted can be obtained by decodingdata output from the signaling decoding module 9400 to restorescheduling information generated by the apparatus for transmittingbroadcast signals.

The demapping & decoding module 9200 can convert the input signals intobit domain data and then deinterleave the same as necessary. Thedemapping & decoding module 9200 can perform demapping for mappingapplied for transmission efficiency and correct an error generated on atransmission channel through decoding. In this case, the demapping &decoding module 9200 can obtain transmission parameters necessary fordemapping and decoding by decoding the data output from the signalingdecoding module 9400.

The output processor 9300 can perform reverse procedures of variouscompression/signal processing procedures which are applied by theapparatus for transmitting broadcast signals to improve transmissionefficiency. In this case, the output processor 9300 can acquirenecessary control information from data output from the signalingdecoding module 9400. The output of the output processor 8300corresponds to a signal input to the apparatus for transmittingbroadcast signals and may be MPEG-TSs, IP streams (v4 or v6) and genericstreams.

The signaling decoding module 9400 can obtain PLS information from thesignal demodulated by the synchronization & demodulation module 9000. Asdescribed above, the frame parsing module 9100, demapping & decodingmodule 9200 and output processor 9300 can execute functions thereofusing the data output from the signaling decoding module 9400.

FIG. 10 illustrates a frame structure according to an embodiment of thepresent invention.

FIG. 10 shows an example configuration of the frame types and FRUs in asuper-frame. (a) shows a super frame according to an embodiment of thepresent invention, (b) shows FRU (Frame Repetition Unit) according to anembodiment of the present invention, (c) shows frames of variable PHYprofiles in the FRU and (d) shows a structure of a frame.

A super-frame may be composed of eight FRUs. The FRU is a basicmultiplexing unit for TDM of the frames, and is repeated eight times ina super-frame.

Each frame in the FRU belongs to one of the PHY profiles, (base,handheld, advanced) or FEF. The maximum allowed number of the frames inthe FRU is four and a given PHY profile can appear any number of timesfrom zero times to four times in the FRU (e.g., base, base, handheld,advanced). PHY profile definitions can be extended using reserved valuesof the PHY PROFILE in the preamble, if required.

The FEF part is inserted at the end of the FRU, if included. When theFEF is included in the FRU, the minimum number of FEFs is 8 in asuper-frame. It is not recommended that FEF parts be adjacent to eachother.

One frame is further divided into a number of OFDM symbols and apreamble. As shown in (d), the frame comprises a preamble, one or moreframe signaling symbols (FSS), normal data symbols and a frame edgesymbol (FES).

The preamble is a special symbol that enables fast Futurecast UTB systemsignal detection and provides a set of basic transmission parameters forefficient transmission and reception of the signal. The detaileddescription of the preamble will be will be described later.

The main purpose of the FSS(s) is to carry the PLS data. For fastsynchronization and channel estimation, and hence fast decoding of PLSdata, the FSS has more dense pilot pattern than the normal data symbol.The FES has exactly the same pilots as the FSS, which enablesfrequency-only interpolation within the FES and temporal interpolation,without extrapolation, for symbols immediately preceding the FES.

FIG. 11 illustrates a signaling hierarchy structure of the frameaccording to an embodiment of the present invention.

FIG. 11 illustrates the signaling hierarchy structure, which is splitinto three main parts: the preamble signaling data 11000, the PLS1 data11010 and the PLS2 data 11020. The purpose of the preamble, which iscarried by the preamble symbol in every frame, is to indicate thetransmission type and basic transmission parameters of that frame. ThePLS1 enables the receiver to access and decode the PLS2 data, whichcontains the parameters to access the DP of interest. The PLS2 iscarried in every frame and split into two main parts: PLS2-STAT data andPLS2-DYN data. The static and dynamic portion of PLS2 data is followedby padding, if necessary.

FIG. 12 illustrates preamble signaling data according to an embodimentof the present invention.

Preamble signaling data carries 21 bits of information that are neededto enable the receiver to access PLS data and trace DPs within the framestructure. Details of the preamble signaling data are as follows:

PHY_PROFILE: This 3-bit field indicates the PHY profile type of thecurrent frame. The mapping of different PHY profile types is given inbelow table 5.

TABLE 5 Value PHY profile 000 Base profile 001 Handheld profile 010Advanced profiled 011~110 Reserved 111 FEF

FFT_SIZE: This 2 bit field indicates the FFT size of the current framewithin a frame-group, as described in below table 6.

TABLE 6 Value FFT size 00  8K FFT 01 16K FFT 10 32K FFT 11 Reserved

GI_FRACTION: This 3 bit field indicates the guard interval fractionvalue in the current super-frame, as described in below table 7.

TABLE 7 Value GI_FRACTION 000 1/5  001 1/10 010 1/20 011 1/40 100 1/80101  1/160 110~111 Reserved

EAC_FLAG: This 1 bit field indicates whether the EAC is provided in thecurrent frame. If this field is set to ‘1’, emergency alert service(EAS) is provided in the current frame. If this field set to ‘0’, EAS isnot carried in the current frame. This field can be switched dynamicallywithin a super-frame.

PILOT_MODE: This 1-bit field indicates whether the pilot mode is mobilemode or fixed mode for the current frame in the current frame-group. Ifthis field is set to ‘0’, mobile pilot mode is used. If the field is setto ‘1’, the fixed pilot mode is used.

PAPR_FLAG: This 1-bit field indicates whether PAPR reduction is used forthe current frame in the current frame-group. If this field is set tovalue ‘1’, tone reservation is used for PAPR reduction. If this field isset to ‘0’, PAPR reduction is not used.

FRU_CONFIGURE: This 3-bit field indicates the PHY profile typeconfigurations of the frame repetition units (FRU) that are present inthe current super-frame. All profile types conveyed in the currentsuper-frame are identified in this field in all preambles in the currentsuper-frame. The 3-bit field has a different definition for eachprofile, as show in below table 8.

TABLE 8 Current Current Current Current PHY_PROFILE = PHY_PROFILE =PHY_PROFILE = PHY_PROFILE = ‘000’ (base) ‘001’ (handheld) ‘010’(advanced) ‘111’ (FEF) FRU_CONFIGURE = Only base Only handheld Onlyadvanced Only FEF 000 profile profile present profile present presentpresent FRU_CONFIGURE = Handheld profile Base profile Base profile Baseprofile 1XX present present present present FRU_CONFIGURE = AdvancedAdvanced Handheld profile Handheld profile X1X profile profile presentpresent present present FRU_CONFIGURE = FEF FEF FEF Advanced XX1 presentpresent present profile present

RESERVED: This 7-bit field is reserved for future use.

FIG. 13 illustrates PLS1 data according to an embodiment of the presentinvention.

PLS1 data provides basic transmission parameters including parametersrequired to enable the reception and decoding of the PLS2. As abovementioned, the PLS1 data remain unchanged for the entire duration of oneframe-group. The detailed definition of the signaling fields of the PLS1data are as follows:

PREAMBLE_DATA: This 20-bit field is a copy of the preamble signalingdata excluding the EAC_FLAG.

NUM_FRAME_FRU: This 2-bit field indicates the number of the frames perFRU.

PAYLOAD_TYPE: This 3-bit field indicates the format of the payload datacarried in the frame-group. PAYLOAD_TYPE is signaled as shown in table9.

TABLE 9 value Payload type 1XX TS stream is transmitted X1X IP stream istransmitted XX1 GS stream is transmittedNUM_FSS: This 2-bit field indicates the number of FSS symbols in thecurrent frame.

SYSTEM_VERSION: This 8-bit field indicates the version of thetransmitted signal format. The SYSTEM_VERSION is divided into two 4-bitfields, which are a major version and a minor version.

Major version: The MSB four bits of SYSTEM_VERSION field indicate majorversion information. A change in the major version field indicates anon-backward-compatible change. The default value is ‘0000’. For theversion described in this standard, the value is set to ‘0000’.

Minor version: The LSB four bits of SYSTEM_VERSION field indicate minorversion information. A change in the minor version field isbackward-compatible.

CELL_ID: This is a 16-bit field which uniquely identifies a geographiccell in an ATSC network. An ATSC cell coverage area may consist of oneor more frequencies, depending on the number of frequencies used perFuturecast UTB system. If the value of the CELL_ID is not known orunspecified, this field is set to ‘0’.

NETWORK_ID: This is a 16-bit field which uniquely identifies the currentATSC network.

SYSTEM_ID: This 16-bit field uniquely identifies the Futurecast UTBsystem within the ATSC network. The Futurecast UTB system is theterrestrial broadcast system whose input is one or more input streams(TS, IP, GS) and whose output is an RF signal. The Futurecast UTB systemcarries one or more PHY profiles and FEF, if any. The same FuturecastUTB system may carry different input streams and use different RFfrequencies in different geographical areas, allowing local serviceinsertion. The frame structure and scheduling is controlled in one placeand is identical for all transmissions within a Futurecast UTB system.One or more Futurecast UTB systems may have the same SYSTEM_ID meaningthat they all have the same physical layer structure and configuration.

The following loop consists of FRU_PHY_PROFILE, FRU_FRAME_LENGTH,FRU_GI_FRACTION, and RESERVED which are used to indicate the FRUconfiguration and the length of each frame type. The loop size is fixedso that four PHY profiles (including a FEF) are signaled within the FRU.If NUM_FRAME_FRU is less than 4, the unused fields are filled withzeros.

FRU_PHY_PROFILE: This 3-bit field indicates the PHY profile type of the(i+1)th (i is the loop index) frame of the associated FRU. This fielduses the same signaling format as shown in the table 8.

FRU_FRAME_LENGTH: This 2-bit field indicates the length of the (i+1)thframe of the associated FRU. Using FRU_FRAME_LENGTH together withFRU_GI_FRACTION, the exact value of the frame duration can be obtained.

FRU_GI_FRACTION: This 3-bit field indicates the guard interval fractionvalue of the (i+1)th frame of the associated FRU. FRU_GI_FRACTION issignaled according to the table 7.

RESERVED: This 4-bit field is reserved for future use.

The following fields provide parameters for decoding the PLS2 data.

PLS2_FEC_TYPE: This 2-bit field indicates the FEC type used by the PLS2protection. The FEC type is signaled according to table 10. The detailsof the LDPC codes will be described later.

TABLE 10 Content PLS2 FEC type 00 4K-1/4 and 7K-3/10 LDPC codes 01~11Reserved

PLS2_MOD: This 3-bit field indicates the modulation type used by thePLS2. The modulation type is signaled according to table 11.

TABLE 11 Value PLS2_MODE 000 BPSK 001 QPSK 010 QAM-16 011 NUQ-64 100~111Reserved

PLS2_SIZE_CELL: This 15-bit field indicates C_(total_partial_block), thesize (specified as the number of QAM cells) of the collection of fullcoded blocks for PLS2 that is carried in the current frame-group. Thisvalue is constant during the entire duration of the current frame-group.

PLS2_STAT_SIZE_BIT: This 14-bit field indicates the size, in bits, ofthe PLS2-STAT for the current frame-group. This value is constant duringthe entire duration of the current frame-group.

PLS2_DYN_SIZE_BIT: This 14-bit field indicates the size, in bits, of thePLS2-DYN for the current frame-group. This value is constant during theentire duration of the current frame-group.

PLS2_REP_FLAG: This 1-bit flag indicates whether the PLS2 repetitionmode is used in the current frame-group. When this field is set to value‘1’, the PLS2 repetition mode is activated. When this field is set tovalue ‘0’, the PLS2 repetition mode is deactivated.

PLS2_REP_SIZE_CELL: This 15-bit field indicates C_(total_partial_block),the size (specified as the number of QAM cells) of the collection ofpartial coded blocks for PLS2 carried in every frame of the currentframe-group, when PLS2 repetition is used. If repetition is not used,the value of this field is equal to 0. This value is constant during theentire duration of the current frame-group.

PLS2_NEXT_FEC_TYPE: This 2-bit field indicates the FEC type used forPLS2 that is carried in every frame of the next frame-group. The FECtype is signaled according to the table 10.

PLS2_NEXT_MOD: This 3-bit field indicates the modulation type used forPLS2 that is carried in every frame of the next frame-group. Themodulation type is signaled according to the table 11.

PLS2_NEXT_REP_FLAG: This 1-bit flag indicates whether the PLS2repetition mode is used in the next frame-group. When this field is setto value ‘1’, the PLS2 repetition mode is activated. When this field isset to value ‘0’, the PLS2 repetition mode is deactivated.

PLS2_NEXT REP_SIZE_CELL: This 15-bit field indicatesC_(total_full_block). The size (specified as the number of QAM cells) ofthe collection of full coded blocks for PLS2 that is carried in everyframe of the next frame-group, when PLS2 repetition is used. Ifrepetition is not used in the next frame-group, the value of this fieldis equal to 0. This value is constant during the entire duration of thecurrent frame-group.

PLS2_NEXT_REP_STAT_SIZE_BIT: This 14-bit field indicates the size, inbits, of the PLS2-STAT for the next frame-group. This value is constantin the current frame-group.

PLS2_NEXT_REP_DYN_SIZE_BIT: This 14-bit field indicates the size, inbits, of the PLS2-DYN for the next frame-group. This value is constantin the current frame-group.

PLS2_AP_MODE: This 2-bit field indicates whether additional parity isprovided for PLS2 in the current frame-group. This value is constantduring the entire duration of the current frame-group. The below table12 gives the values of this field. When this field is set to ‘00’,additional parity is not used for the PLS2 in the current frame-group.

TABLE 12 Value PLS2-AP mode 00 AP is not provided 01 AP1 mode 10~11Reserved

PLS2_AP_SIZE_CELL: This 15-bit field indicates the size (specified asthe number of QAM cells) of the additional parity bits of the PLS2. Thisvalue is constant during the entire duration of the current frame-group.

PLS2_NEXT_AP_MODE: This 2-bit field indicates whether additional parityis provided for PLS2 signaling in every frame of next frame-group. Thisvalue is constant during the entire duration of the current frame-group.The table 12 defines the values of this field.

PLS2_NEXT_AP_SIZE_CELL: This 15-bit field indicates the size (specifiedas the number of QAM cells) of the additional parity bits of the PLS2 inevery frame of the next frame-group. This value is constant during theentire duration of the current frame-group.

RESERVED: This 32-bit field is reserved for future use.

CRC_32: A 32-bit error detection code, which is applied to the entirePLS1 signaling.

FIG. 14 illustrates PLS2 data according to an embodiment of the presentinvention.

FIG. 14 illustrates PLS2-STAT data of the PLS2 data. The PLS2-STAT dataare the same within a frame-group, while the PLS2-DYN data provideinformation that is specific for the current frame.

The details of fields of the PLS2-STAT data are as follows:

FIC_FLAG: This 1-bit field indicates whether the FIC is used in thecurrent frame-group. If this field is set to ‘1’, the FIC is provided inthe current frame. If this field set to ‘0’, the FIC is not carried inthe current frame. This value is constant during the entire duration ofthe current frame-group.

AUX_FLAG: This 1-bit field indicates whether the auxiliary stream(s) isused in the current frame-group. If this field is set to ‘1’, theauxiliary stream is provided in the current frame. If this field set to‘0’, the auxiliary stream is not carried in the current frame. Thisvalue is constant during the entire duration of current frame-group.

NUM_DP: This 6-bit field indicates the number of DPs carried within thecurrent frame. The value of this field ranges from 1 to 64, and thenumber of DPs is NUM_DP+1.

DP_ID: This 6-bit field identifies uniquely a DP within a PHY profile.

DP_TYPE: This 3-bit field indicates the type of the DP. This is signaledaccording to the below table 13.

TABLE 13 Value DP Type 000 DP Type 1 001 DP Type 2 010~111 reserved

DP_GROUP_ID: This 8-bit field identifies the DP group with which thecurrent DP is associated. This can be used by a receiver to access theDPs of the service components associated with a particular service,which will have the same DP_GROUP_ID.

BASE_DP_ID: This 6-bit field indicates the DP carrying service signalingdata (such as PSI/SI) used in the Management layer. The DP indicated byBASE_DP_ID may be either a normal DP carrying the service signaling dataalong with the service data or a dedicated DP carrying only the servicesignaling data.

DP_FEC_TYPE: This 2-bit field indicates the FEC type used by theassociated DP. The FEC type is signaled according to the below table 14.

TABLE 14 Value FEC_TYPE 00 16K LDPC 01 64K LDPC 10~11 Reserved

DP_COD: This 4-bit field indicates the code rate used by the associatedDP. The code rate is signaled according to the below table 15.

TABLE 15 Value Code rate 0000 5/15 0001 6/15 0010 7/15 0011 8/15 01009/15 0101 10/15  0110 11/15  0111 12/15  1000 13/15  1001~1111 Reserved

DP_MOD: This 4-bit field indicates the modulation used by the associatedDP. The modulation is signaled according to the below table 16.

TABLE 16 Value Modulation 0000 QPSK 0001 QAM-16 0010 NUQ-64 0011 NUQ-2560100 NUQ-1024 0101 NUC-16 0110 NUC-64 0111 NUC-256 1000 NUC-10241001~1111 reserved

DP_SSD_FLAG: This 1-bit field indicates whether the SSD mode is used inthe associated DP. If this field is set to value ‘1’, SSD is used. Ifthis field is set to value ‘0’, SSD is not used.

The following field appears only if PHY_PROFILE is equal to ‘010’, whichindicates the advanced profile:

DP_MIMO: This 3-bit field indicates which type of MIMO encoding processis applied to the associated DP. The type of MIMO encoding process issignaled according to the table 17.

TABLE 17 Value MIMO encoding 000 FR-SM 001 FRFD-SM 010~111 reserved

DP_TI_TYPE: This 1-bit field indicates the type of time-interleaving. Avalue of ‘0’ indicates that one TI group corresponds to one frame andcontains one or more TI-blocks. A value of ‘1’ indicates that one TIgroup is carried in more than one frame and contains only one TI-block.

DP_TI_LENGTH: The use of this 2-bit field (the allowed values are only1, 2, 4, 8) is determined by the values set within the DP_TI_TYPE fieldas follows:

If the DP_TI_TYPE is set to the value ‘1’, this field indicates P_(I),the number of the frames to which each TI group is mapped, and there isone TI-block per TI group (NTI=1). The allowed P_(I) values with 2-bitfield are defined in the below table 18.

If the DP_TI_TYPE is set to the value ‘0’, this field indicates thenumber of TI-blocks N_(TI) per TI group, and there is one TI group perframe (P_(I)=1). The allowed P_(I) values with 2-bit field are definedin the below table 18.

TABLE 18 2-bit field P_(I) N_(TI) 00 1 1 01 2 2 10 4 3 11 8 4

DP_FRAME_INTERVAL: This 2-bit field indicates the frame interval(I_(JUMP)) within the frame-group for the associated DP and the allowedvalues are 1, 2, 4, 8 (the corresponding 2-bit field is ‘00’, ‘01’,‘10’, or ‘11’, respectively). For DPs that do not appear every frame ofthe frame-group, the value of this field is equal to the intervalbetween successive frames. For example, if a DP appears on the frames 1,5, 9, 13, etc., this field is set to ‘4’. For DPs that appear in everyframe, this field is set to ‘1’.

DP_TI_BYPASS: This 1-bit field determines the availability of timeinterleaver. If time interleaving is not used for a DP, it is set to‘1’. Whereas if time interleaving is used it is set to ‘0’.

DP_FIRST_FRAME_IDX: This 5-bit field indicates the index of the firstframe of the super-frame in which the current DP occurs. The value ofDP_FIRST_FRAME_IDX ranges from 0 to 31

DP_NUM_BLOCK_MAX: This 10-bit field indicates the maximum value ofDP_NUM_BLOCKS for this DP. The value of this field has the same range asDP_NUM_BLOCKS.

DP_PAYLOAD_TYPE: This 2-bit field indicates the type of the payload datacarried by the given DP. DP_PAYLOAD_TYPE is signaled according to thebelow table 19.

TABLE 19 Value Payload Type 00 TS. 01 IP 10 GS 11 reserved

DP_INBAND_MODE: This 2-bit field indicates whether the current DPcarries in-band signaling information. The in-band signaling type issignaled according to the below table 20.

TABLE 20 Value In-band mode 00 In-band signaling is not carried. 01INBAND-PLS is carried only 10 INBAND-ISSY is carried only 11 INBAND-PLSand INBAND-ISSY are carried

DP_PROTOCOL_TYPE: This 2-bit field indicates the protocol type of thepayload carried by the given DP. It is signaled according to the belowtable 21 when input payload types are selected.

TABLE 21 If DP_PAY- If DP_PAY- If DP_PAY- LOAD_TYPE LOAD_TYPE LOAD_TYPEValue Is TS Is IP Is GS 00 MPEG2-TS IPv4 (Note) 01 Reserved IPv6Reserved 10 Reserved Reserved Reserved 11 Reserved Reserved Reserved

DP_CRC_MODE: This 2-bit field indicates whether CRC encoding is used inthe Input Formatting block. The CRC mode is signaled according to thebelow table 22.

TABLE 22 Value CRC mode 00 Not used 01 CRC-8 10 CRC-16 11 CRC-32

DNP_MODE: This 2-bit field indicates the null-packet deletion mode usedby the associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). DNP_MODEis signaled according to the below table 23. If DP_PAYLOAD_TYPE is notTS (‘00’), DNP_MODE is set to the value ‘00’.

TABLE 23 Value Null-packet deletion mode 00 Not used 01 DNP-NORMAL 10DNP-OFFSET 11 reserved

ISSY_MODE: This 2-bit field indicates the ISSY mode used by theassociated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). The ISSY_MODE issignaled according to the below table 24 If DP_PAYLOAD_TYPE is not TS(‘00’), ISSY_MODE is set to the value ‘00’.

TABLE 24 Value ISSY mode 00 Not used 01 ISSY-UP 10 ISSY-BBF 11 reserved

HC_MODE_TS: This 2-bit field indicates the TS header compression modeused by the associated DP when DP_PAYLOAD_TYPE is set to TS (‘00’). TheHC_MODE_TS is signaled according to the below table 25.

TABLE 25 Value Header compression mode 00 HC_MODE_TS 1 01 HC_MODE_TS 210 HC_MODE_TS 3 11 HC_MODE_TS 4

HC_MODE_IP: This 2-bit field indicates the IP header compression modewhen DP_PAYLOAD_TYPE is set to IP (‘01’). The HC_MODE_IP is signaledaccording to the below table 26.

TABLE 26 Value Header compression mode 00 No compression 01 HC_MODE_IP 110~11 reserved

PID: This 13-bit field indicates the PID number for TS headercompression when DP_PAYLOAD_TYPE is set to TS (‘00’) and HC_MODE_TS isset to ‘01’ or ‘10’.

RESERVED: This 8-bit field is reserved for future use.

The following field appears only if FIC_FLAG is equal to T:

FIC_VERSION: This 8-bit field indicates the version number of the FIC.

FIC_LENGTH_BYTE: This 13-bit field indicates the length, in bytes, ofthe FIC.

RESERVED: This 8-bit field is reserved for future use.

The following field appears only if AUX_FLAG is equal to ‘1’:

NUM_AUX: This 4-bit field indicates the number of auxiliary streams.Zero means no auxiliary streams are used.

AUX_CONFIG_RFU: This 8-bit field is reserved for future use.

AUX_STREAM_TYPE: This 4-bit is reserved for future use for indicatingthe type of the current auxiliary stream.

AUX_PRIVATE_CONFIG: This 28-bit field is reserved for future use forsignaling auxiliary streams.

FIG. 15 illustrates PLS2 data according to another embodiment of thepresent invention.

FIG. 15 illustrates PLS2-DYN data of the PLS2 data. The values of thePLS2-DYN data may change during the duration of one frame-group, whilethe size of fields remains constant.

The details of fields of the PLS2-DYN data are as follows:

FRAME_INDEX: This 5-bit field indicates the frame index of the currentframe within the super-frame. The index of the first frame of thesuper-frame is set to ‘0’.

PLS_CHANGE_COUNTER: This 4-bit field indicates the number ofsuper-frames ahead where the configuration will change. The nextsuper-frame with changes in the configuration is indicated by the valuesignaled within this field. If this field is set to the value ‘0000’, itmeans that no scheduled change is foreseen: e.g., value ‘1’ indicatesthat there is a change in the next super-frame.

FIC_CHANGE_COUNTER: This 4-bit field indicates the number ofsuper-frames ahead where the configuration (i.e., the contents of theFIC) will change. The next super-frame with changes in the configurationis indicated by the value signaled within this field. If this field isset to the value ‘0000’, it means that no scheduled change is foreseen:e.g. value ‘0001’ indicates that there is a change in the nextsuper-frame.

RESERVED: This 16-bit field is reserved for future use.

The following fields appear in the loop over NUM_DP, which describe theparameters associated with the DP carried in the current frame.

DP_ID: This 6-bit field indicates uniquely the DP within a PHY profile.

DP_START: This 15-bit (or 13-bit) field indicates the start position ofthe first of the DPs using the DPU addressing scheme. The DP_START fieldhas differing length according to the PHY profile and FFT size as shownin the below table 27.

TABLE 27 DP_START field size PHY profile 64K 16K Base 13 bit 15 bitHandheld — 13 bit Advanced 13 bit 15 bit

DP_NUM_BLOCK: This 10-bit field indicates the number of FEC blocks inthe current TI group for the current DP. The value of DP_NUM_BLOCKranges from 0 to 1023.

RESERVED: This 8-bit field is reserved for future use.

The following fields indicate the FIC parameters associated with theEAC.

EAC_FLAG: This 1-bit field indicates the existence of the EAC in thecurrent frame. This bit is the same value as the EAC_FLAG in thepreamble.

EAS_WAKE_UP_VERSION_NUM: This 8-bit field indicates the version numberof a wake-up indication.

If the EAC_FLAG field is equal to ‘1’, the following 12 bits areallocated for EAC_LENGTH_BYTE field. If the EAC_FLAG field is equal to‘0’, the following 12 bits are allocated for EAC_COUNTER.

EAC_LENGTH_BYTE: This 12-bit field indicates the length, in byte, of theEAC.

EAC_COUNTER: This 12-bit field indicates the number of the frames beforethe frame where the EAC arrives.

The following field appears only if the AUX_FLAG field is equal to ‘1’:

AUX_PRIVATE_DYN: This 48-bit field is reserved for future use forsignaling auxiliary streams. The meaning of this field depends on thevalue of AUX_STREAM_TYPE in the configurable PLS2-STAT.

CRC_32: A 32-bit error detection code, which is applied to the entirePLS2.

FIG. 16 illustrates a logical structure of a frame according to anembodiment of the present invention.

As above mentioned, the PLS, EAC, FIC, DPs, auxiliary streams and dummycells are mapped into the active carriers of the OFDM symbols in theframe. The PLS1 and PLS2 are first mapped into one or more FSS(s). Afterthat, EAC cells, if any, are mapped immediately following the PLS field,followed next by FIC cells, if any. The DPs are mapped next after thePLS or EAC, FIC, if any. Type 1 DPs follows first, and Type 2 DPs next.The details of a type of the DP will be described later. In some case,DPs may carry some special data for EAS or service signaling data. Theauxiliary stream or streams, if any, follow the DPs, which in turn arefollowed by dummy cells. Mapping them all together in the abovementioned order, i.e. PLS, EAC, FIC, DPs, auxiliary streams and dummydata cells exactly fill the cell capacity in the frame.

FIG. 17 illustrates PLS mapping according to an embodiment of thepresent invention.

PLS cells are mapped to the active carriers of FSS(s). Depending on thenumber of cells occupied by PLS, one or more symbols are designated asFSS(s), and the number of FSS(s) NFSS is signaled by NUM_FSS in PLS1.The FSS is a special symbol for carrying PLS cells. Since robustness andlatency are critical issues in the PLS, the FSS(s) has higher density ofpilots allowing fast synchronization and frequency-only interpolationwithin the FSS.

PLS cells are mapped to active carriers of the NFSS FSS(s) in a top-downmanner as shown in an example in FIG. 17. The PLS1 cells are mappedfirst from the first cell of the first FSS in an increasing order of thecell index. The PLS2 cells follow immediately after the last cell of thePLS1 and mapping continues downward until the last cell index of thefirst FSS. If the total number of required PLS cells exceeds the numberof active carriers of one FSS, mapping proceeds to the next FSS andcontinues in exactly the same manner as the first FSS.

After PLS mapping is completed, DPs are carried next. If EAC, FIC orboth are present in the current frame, they are placed between PLS and“normal” DPs.

FIG. 18 illustrates EAC mapping according to an embodiment of thepresent invention.

EAC is a dedicated channel for carrying EAS messages and links to theDPs for EAS. EAS support is provided but EAC itself may or may not bepresent in every frame. EAC, if any, is mapped immediately after thePLS2 cells. EAC is not preceded by any of the FIC, DPs, auxiliarystreams or dummy cells other than the PLS cells. The procedure ofmapping the EAC cells is exactly the same as that of the PLS.

The EAC cells are mapped from the next cell of the PLS2 in increasingorder of the cell index as shown in the example in FIG. 18. Depending onthe EAS message size, EAC cells may occupy a few symbols, as shown inFIG. 18.

EAC cells follow immediately after the last cell of the PLS2, andmapping continues downward until the last cell index of the last FSS. Ifthe total number of required EAC cells exceeds the number of remainingactive carriers of the last FSS mapping proceeds to the next symbol andcontinues in exactly the same manner as FSS(s). The next symbol formapping in this case is the normal data symbol, which has more activecarriers than a FSS.

After EAC mapping is completed, the FIC is carried next, if any exists.If FIC is not transmitted (as signaled in the PLS2 field), DPs followimmediately after the last cell of the EAC.

FIG. 19 illustrates FIC mapping according to an embodiment of thepresent invention.

(a) shows an example mapping of FIC cell without EAC and (b) shows anexample mapping of FIC cell with EAC.

FIC is a dedicated channel for carrying cross-layer information toenable fast service acquisition and channel scanning. This informationprimarily includes channel binding information between DPs and theservices of each broadcaster. For fast scan, a receiver can decode FICand obtain information such as broadcaster ID, number of services, andBASE_DP_ID. For fast service acquisition, in addition to FIC, base DPcan be decoded using BASE_DP_ID. Other than the content it carries, abase DP is encoded and mapped to a frame in exactly the same way as anormal DP. Therefore, no additional description is required for a baseDP. The FIC data is generated and consumed in the Management Layer. Thecontent of FIC data is as described in the Management Layerspecification.

The FIC data is optional and the use of FIC is signaled by the FIC_FLAGparameter in the static part of the PLS2. If FIC is used, FIC_FLAG isset to ‘1’ and the signaling field for FIC is defined in the static partof PLS2. Signaled in this field are FIC_VERSION, and FIC_LENGTH_BYTE.FIC uses the same modulation, coding and time interleaving parameters asPLS2. FIC shares the same signaling parameters such as PLS2_MOD andPLS2_FEC. FIC data, if any, is mapped immediately after PLS2 or EAC ifany. FIC is not preceded by any normal DPs, auxiliary streams or dummycells. The method of mapping FIC cells is exactly the same as that ofEAC which is again the same as PLS.

Without EAC after PLS, FIC cells are mapped from the next cell of thePLS2 in an increasing order of the cell index as shown in an example in(a). Depending on the FIC data size, FIC cells may be mapped over a fewsymbols, as shown in (b).

FIC cells follow immediately after the last cell of the PLS2, andmapping continues downward until the last cell index of the last FSS. Ifthe total number of required FIC cells exceeds the number of remainingactive carriers of the last FSS, mapping proceeds to the next symbol andcontinues in exactly the same manner as FSS(s). The next symbol formapping in this case is the normal data symbol which has more activecarriers than a FSS.

If EAS messages are transmitted in the current frame, EAC precedes FIC,and FIC cells are mapped from the next cell of the EAC in an increasingorder of the cell index as shown in (b).

After FIC mapping is completed, one or more DPs are mapped, followed byauxiliary streams, if any, and dummy cells.

FIG. 20 illustrates a type of DP according to an embodiment of thepresent invention.

(a) shows type 1 DP and (b) shows type 2 DP.

After the preceding channels, i.e., PLS, EAC and FIC, are mapped, cellsof the DPs are mapped. A DP is categorized into one of two typesaccording to mapping method:

Type 1 DP: DP is mapped by TDM

Type 2 DP: DP is mapped by FDM

The type of DP is indicated by DP_TYPE field in the static part of PLS2.FIG. 20 illustrates the mapping orders of Type 1 DPs and Type 2 DPs.Type 1 DPs are first mapped in the increasing order of cell index, andthen after reaching the last cell index, the symbol index is increasedby one. Within the next symbol, the DP continues to be mapped in theincreasing order of cell index starting from p=0. With a number of DPsmapped together in one frame, each of the Type 1 DPs are grouped intime, similar to TDM multiplexing of DPs.

Type 2 DPs are first mapped in the increasing order of symbol index, andthen after reaching the last OFDM symbol of the frame, the cell indexincreases by one and the symbol index rolls back to the first availablesymbol and then increases from that symbol index. After mapping a numberof DPs together in one frame, each of the Type 2 DPs are grouped infrequency together, similar to FDM multiplexing of DPs.

Type 1 DPs and Type 2 DPs can coexist in a frame if needed with onerestriction; Type 1 DPs always precede Type 2 DPs. The total number ofOFDM cells carrying Type 1 and Type 2 DPs cannot exceed the total numberof OFDM cells available for transmission of DPs:

D _(DP)1+D _(DP2) ≤D _(DP)  [Math FIG. 2]

where DDP1 is the number of OFDM cells occupied by Type 1 DPs, DDP2 isthe number of cells occupied by Type 2 DPs. Since PLS, EAC, FIC are allmapped in the same way as Type 1 DP, they all follow “Type 1 mappingrule”. Hence, overall, Type 1 mapping always precedes Type 2 mapping.

FIG. 21 illustrates DP mapping according to an embodiment of the presentinvention.

(a) shows an addressing of OFDM cells for mapping type 1 DPs and (b)shows an addressing of OFDM cells for mapping for type 2 DPs.

Addressing of OFDM cells for mapping Type 1 DPs (0, . . . , DDP11) isdefined for the active data cells of Type 1 DPs. The addressing schemedefines the order in which the cells from the TIs for each of the Type 1DPs are allocated to the active data cells. It is also used to signalthe locations of the DPs in the dynamic part of the PLS2.

Without EAC and FIC, address 0 refers to the cell immediately followingthe last cell carrying PLS in the last FSS. If EAC is transmitted andFIC is not in the corresponding frame, address 0 refers to the cellimmediately following the last cell carrying EAC. If FIC is transmittedin the corresponding frame, address 0 refers to the cell immediatelyfollowing the last cell carrying FIC. Address 0 for Type 1 DPs can becalculated considering two different cases as shown in (a). In theexample in (a), PLS, EAC and FIC are assumed to be all transmitted.Extension to the cases where either or both of EAC and FIC are omittedis straightforward. If there are remaining cells in the FSS aftermapping all the cells up to FIC as shown on the left side of (a).

Addressing of OFDM cells for mapping Type 2 DPs (0, . . . , DDP21) isdefined for the active data cells of Type 2 DPs. The addressing schemedefines the order in which the cells from the TIs for each of the Type 2DPs are allocated to the active data cells. It is also used to signalthe locations of the DPs in the dynamic part of the PLS2.

Three slightly different cases are possible as shown in (b). For thefirst case shown on the left side of (b), cells in the last FSS areavailable for Type 2 DP mapping. For the second case shown in themiddle, FIC occupies cells of a normal symbol, but the number of FICcells on that symbol is not larger than C_(FSS). The third case, shownon the right side in (b), is the same as the second case except that thenumber of FIC cells mapped on that symbol exceeds C_(FSS).

The extension to the case where Type 1 DP(s) precede Type 2 DP(s) isstraightforward since PLS, EAC and FIC follow the same “Type 1 mappingrule” as the Type 1 DP(s).

A data pipe unit (DPU) is a basic unit for allocating data cells to a DPin a frame.

A DPU is defined as a signaling unit for locating DPs in a frame. A CellMapper 7010 may map the cells produced by the TIs for each of the DPs. ATime interleaver 5050 outputs a series of TI-blocks and each TI-blockcomprises a variable number of XFECBLOCKs which is in turn composed of aset of cells. The number of cells in an XFECBLOCK, N_(cells), isdependent on the FECBLOCK size, N_(ldpc), and the number of transmittedbits per constellation symbol. A DPU is defined as the greatest commondivisor of all possible values of the number of cells in a XFECBLOCK,N_(cells), supported in a given PHY profile. The length of a DPU incells is defined as L_(DPU). Since each PHY profile supports differentcombinations of FECBLOCK size and a different number of bits perconstellation symbol, L_(DPU) is defined on a PHY profile basis.

FIG. 22 illustrates an FEC structure according to an embodiment of thepresent invention.

FIG. 22 illustrates an FEC structure according to an embodiment of thepresent invention before bit interleaving. As above mentioned, Data FECencoder may perform the FEC encoding on the input BBF to generateFECBLOCK procedure using outer coding (BCH), and inner coding (LDPC).The illustrated FEC structure corresponds to the FECBLOCK. Also, theFECBLOCK and the FEC structure have same value corresponding to a lengthof LDPC codeword.

The BCH encoding is applied to each BBF (K_(bch) bits), and then LDPCencoding is applied to BCH-encoded BBF (K_(ldpc) bits=N_(bch) bits) asillustrated in FIG. 22.

The value of N_(ldpc) is either 64800 bits (long FECBLOCK) or 16200 bits(short FECBLOCK).

The below table 28 and table 29 show FEC encoding parameters for a longFECBLOCK and a short FECBLOCK, respectively.

TABLE 28 BCH error LDPC correction Rate N_(ldpc) K_(ldpc) K_(bch)capability N_(bch) − K_(bch) 5/15 64800 21600 21408 12 192 6/15 2592025728 7/15 30240 30048 8/15 34560 34368 9/15 38880 38688 10/15  4320043008 11/15  47520 47328 12/15  51840 51648 13/15  56160 55968

TABLE 29 BCH error LDPC correction Rate N_(ldpc) K_(ldpc) K_(bch)capability N_(bch) − K_(bch) 5/15 16200 5400 5232 12 168 6/15 6480 63127/15 7560 7392 8/15 8640 8472 9/15 9720 9552 10/15  10800 10632 11/15 11880 11712 12/15  12960 12792 13/15  14040 13872

The details of operations of the BCH encoding and LDPC encoding are asfollows:

A 12-error correcting BCH code is used for outer encoding of the BBF.The BCH generator polynomial for short FECBLOCK and long FECBLOCK areobtained by multiplying together all polynomials.

LDPC code is used to encode the output of the outer BCH encoding. Togenerate a completed B_(ldpc) (FECBLOCK), P_(ldpc) (parity bits) isencoded systematically from each I_(ldpc) (BCH-encoded BBF), andappended to I_(ldpc). The completed Bldpc (FECBLOCK) are expressed asfollow Math figure.

B _(ldpc)=[I _(ldpc) P _(ldpc)]=[i ₀ ,i ₁ , . . . ,i _(K) _(ldpc) ₋₁ ,p₀ ,p ₁ , . . . ,p _(N) _(ldpc) _(-K) _(ldpc) ₋₁]  [Math FIG. 3]

The parameters for long FECBLOCK and short FECBLOCK are given in theabove table 28 and 29, respectively.

The detailed procedure to calculate N_(ldpc)-K_(ldpc) parity bits forlong FECBLOCK, is as follows:

1) Initialize the parity bits,

p ₀ =p ₁ =p ₂ = . . . =p _(N) _(ldpc) _(-K) _(ldpc) ₋₁=0  [Math FIG. 4]

2) Accumulate the first information bit-i0, at parity bit addressesspecified in the first row of an addresses of parity check matrix. Thedetails of addresses of parity check matrix will be described later. Forexample, for rate 13/15:

$\begin{matrix}\begin{matrix}{p_{983} = {p_{983} \oplus i_{0}}} & \; & \; & \; & {p_{2815} = {p_{2815} \oplus i_{0}}} \\{p_{4837} = {p_{4837} \oplus i_{0}}} & \; & \; & \; & {p_{4989} = {p_{4989} \oplus i_{0}}} \\{p_{6138} = {p_{6138} \oplus i_{0}}} & \; & \; & \; & {p_{6458} = {p_{6458} \oplus i_{0}}} \\{p_{6921} = {p_{6921} \oplus i_{0}}} & \; & \; & \; & {p_{6974} = {p_{6974} \oplus i_{0}}} \\{p_{7572} = {p_{7572} \oplus i_{0}}} & \; & \; & \; & {p_{8260} = {p_{8260} \oplus i_{0}}} \\{p_{8496} = {p_{8496} \oplus i_{0}}} & \; & \; & \; & \;\end{matrix} & \lbrack {{Math}\mspace{14mu} {Figure}\mspace{14mu} 5} \rbrack\end{matrix}$

3) For the next 359 information bits, i_(s), s=1, 2, . . . , 359accumulate is at parity bit addresses using following Math figure.

{x+(s mod 360)×Q _(ldpc)} mod(N _(ldpc) −K _(ldpc))  [Math FIG. 6]

where x denotes the address of the parity bit accumulator correspondingto the first bit i₀, and Q_(ldpc) is a code rate dependent constantspecified in the addresses of parity check matrix. Continuing with theexample, Q_(ldpc)=24 for rate 13/15, so for information bit i₁, thefollowing operations are performed:

$\begin{matrix}\begin{matrix}{p_{1007} = {p_{1007} \oplus i_{1}}} & \; & \; & \; & {p_{2839} = {p_{2839} \oplus i_{1}}} \\{p_{4861} = {p_{4861} \oplus i_{1}}} & \; & \; & \; & {p_{5013} = {p_{5013} \oplus i_{1}}} \\{p_{6162} = {p_{6162} \oplus i_{1}}} & \; & \; & \; & {p_{6482} = {p_{6482} \oplus i_{1}}} \\{p_{6945} = {p_{6945} \oplus i_{1}}} & \; & \; & \; & {p_{6998} = {p_{6998} \oplus i_{1}}} \\{p_{7596} = {p_{7596} \oplus i_{1}}} & \; & \; & \; & {p_{8284} = {p_{8284} \oplus i_{1}}} \\{p_{8520} = {p_{8520} \oplus i_{1}}} & \; & \; & \; & \;\end{matrix} & \lbrack {{Math}\mspace{14mu} {Figure}\mspace{14mu} 7} \rbrack\end{matrix}$

4) For the 361st information bit i₃₆₀, the addresses of the parity bitaccumulators are given in the second row of the addresses of paritycheck matrix. In a similar manner the addresses of the parity bitaccumulators for the following 359 information bits i_(s), s=361, 362, .. . , 719 are obtained using the Math FIG. 6, where x denotes theaddress of the parity bit accumulator corresponding to the informationbit i₃₆₀, i.e., the entries in the second row of the addresses of paritycheck matrix.

5) In a similar manner, for every group of 360 new information bits, anew row from addresses of parity check matrixes used to find theaddresses of the parity bit accumulators.

After all of the information bits are exhausted, the final parity bitsare obtained as follows:

6) Sequentially perform the following operations starting with i=1.

p _(i) =p _(i) ⊕p _(i-1) , i=1,2, . . . ,N _(ldpc) −K _(ldpc)−1  [MathFIG. 8]

where final content of p_(i), i=0, 1, . . . N_(ldpc)−K_(ldpc)−1 is equalto the parity bit p_(i).

TABLE 30 Code Rate Q_(ldpc) 5/15 120 6/15 108 7/15 96 8/15 84 9/15 7210/15  60 11/15  48 12/15  36 13/15  24

This LDPC encoding procedure for a short FECBLOCK is in accordance witht LDPC encoding procedure for the long FECBLOCK, except replacing thetable 30 with table 31, and replacing the addresses of parity checkmatrix for the long FECBLOCK with the addresses of parity check matrixfor the short FECBLOCK.

TABLE 31 Code Rate Q_(ldpc) 5/15 30 6/15 27 7/15 24 8/15 21 9/15 1810/15  15 11/15  12 12/15  9 13/15  6

FIG. 23 illustrates a bit interleaving according to an embodiment of thepresent invention.

The outputs of the LDPC encoder are bit-interleaved, which consists ofparity interleaving followed by Quasi-Cyclic Block (QCB) interleavingand inner-group interleaving.

(a) shows Quasi-Cyclic Block (QCB) interleaving and (b) showsinner-group interleaving.

The FECBLOCK may be parity interleaved. At the output of the parityinterleaving, the LDPC codeword consists of 180 adjacent QC blocks in along FECBLOCK and 45 adjacent QC blocks in a short FECBLOCK. Each QCblock in either a long or short FECBLOCK consists of 360 bits. Theparity interleaved LDPC codeword is interleaved by QCB interleaving. Theunit of QCB interleaving is a QC block. The QC blocks at the output ofparity interleaving are permutated by QCB interleaving as illustrated inFIG. 23, where N_(cells)=64800/η_(mod) or 16200/η_(mod) according to theFECBLOCK length. The QCB interleaving pattern is unique to eachcombination of modulation type and LDPC code rate.

After QCB interleaving, inner-group interleaving is performed accordingto modulation type and order (η_(mod)) which is defined in the belowtable 32. The number of QC blocks for one inner-group, N_(QCB_IG), isalso defined.

TABLE 32 Modulation type η_(mod) N_(QCB) _(—) _(IG) QAM-16  4 2 NUC-16 44 NUQ-64 6 3 NUC-64 6 6  NUQ-256 8 4  NUC-256 8 8  NUQ-1024 10 5 NUC-1024 10 10

The inner-group interleaving process is performed with N_(QCB_IG) QCblocks of the QCB interleaving output. Inner-group interleaving has aprocess of writing and reading the bits of the inner-group using 360columns and N_(QCB_IG) rows. In the write operation, the bits from theQCB interleaving output are written row-wise. The read operation isperformed column-wise to read out m bits from each row, where m is equalto 1 for NUC and 2 for NUQ.

FIG. 24 illustrates a cell-word demultiplexing according to anembodiment of the present invention.

(a) shows a cell-word demultiplexing for 8 and 12 bpcu MIMO and (b)shows a cell-word demultiplexing for 10 bpcu MIMO.

Each cell word (c_(0,1), c_(1,1), . . . , c_(nmod-1,1)) of the bitinterleaving output is demultiplexed into (d_(1,0,m), d_(1,1,m) . . .d_(1,nmod-1,m)) and (d_(2,0,m), d_(2,1,m) . . . , d_(2,nmod-1,m)) asshown in (a), which describes the cell-word demultiplexing process forone XFECBLOCK.

For the 10 bpcu MIMO case using different types of NUQ for MIMOencoding, the Bit Interleaver for NUQ-1024 is re-used. Each cell word(c_(0,1), c_(1,1), . . . , c_(9,1)) of the Bit Interleaver output isdemultiplexed into (d_(1,0,m), d_(1,1,m) . . . , d_(1,3,m)) and(d_(2,0,m), d_(2,1,m) . . . , d_(2,5,m)), as shown in (b).

FIG. 25 illustrates a time interleaving according to an embodiment ofthe present invention.

(a) to (c) show examples of TI mode.

The time interleaver operates at the DP level. The parameters of timeinterleaving (TI) may be set differently for each DP.

The following parameters, which appear in part of the PLS2-STAT data,configure the TI:

DP_TI_TYPE (allowed values: 0 or 1): Represents the TI mode; ‘0’indicates the mode with multiple TI blocks (more than one TI block) perTI group. In this case, one TI group is directly mapped to one frame (nointer-frame interleaving). ‘1’ indicates the mode with only one TI blockper TI group. In this case, the TI block may be spread over more thanone frame (inter-frame interleaving).

DP_TI_LENGTH: If DP_TI_TYPE=‘0’, this parameter is the number of TIblocks NTT per TI group. For DP_TI_TYPE=‘1’, this parameter is thenumber of frames PI spread from one TI group.

DP_NUM_BLOCK_MAX (allowed values: 0 to 1023): Represents the maximumnumber of XFECBLOCKs per TI group.

DP_FRAME_INTERVAL (allowed values: 1, 2, 4, 8): Represents the number ofthe frames HUMP between two successive frames carrying the same DP of agiven PHY profile.

DP_TI_BYPASS (allowed values: 0 or 1): If time interleaving is not usedfor a DP, this parameter is set to ‘1’. It is set to ‘0’ if timeinterleaving is used.

Additionally, the parameter DP_NUM_BLOCK from the PLS2-DYN data is usedto represent the number of XFECBLOCKs carried by one TI group of the DP.

When time interleaving is not used for a DP, the following TI group,time interleaving operation, and TI mode are not considered. However,the Delay Compensation block for the dynamic configuration informationfrom the scheduler will still be required. In each DP, the XFECBLOCKsreceived from the SSD/MIMO encoding are grouped into TI groups. That is,each TI group is a set of an integer number of XFECBLOCKs and willcontain a dynamically variable number of XFECBLOCKs. The number ofXFECBLOCKs in the TI group of index n is denoted by N_(xBLOCK_Group)(n)and is signaled as DP_NUM_BLOCK in the PLS2-DYN data. Note thatN_(xBLOCK_Group)(n) may vary from the minimum value of 0 to the maximumvalue N_(xBLOCK_Group_Max) (corresponding to DP_NUM_BLOCK_MAX) of whichthe largest value is 1023.

Each TI group is either mapped directly onto one frame or spread overP_(I) frames. Each TI group is also divided into more than one TIblocks(N_(TI)), where each TI block corresponds to one usage of timeinterleaver memory. The TI blocks within the TI group may containslightly different numbers of XFECBLOCKs. If the TI group is dividedinto multiple TI blocks, it is directly mapped to only one frame. Thereare three options for time interleaving (except the extra option ofskipping the time interleaving) as shown in the below table 33.

TABLE 33 Modes Descriptions Op- Each TI group contains one TI block andis mapped directly to tion-1 one frame as shown in (a). This option issignaled in the PLS2- STAT by DP_TI_TYPE = ‘0’ and DP_TI_LENGTH =‘1’(N_(TI) = 1). Op- Each TI group contains one TI block and is mappedto more than tion-2 one frame. (b) shows an example, where one TI groupis mapped to two frames, i.e., DP_TI_LENGTH = ‘2’ (P_(I) = 2) andDP_FRAME_INTERVAL (I_(JUMP) = 2). This provides greater time diversityfor low data-rate services. This option is signaled in the PLS2-STAT byDP_TI_TYPE = ‘1’. Op- Each TI group is divided into multiple TI blocksand is mapped tion-3 directly to one frame as shown in (c). Each TIblock may use full TI memory, so as to provide the maximum bit-rate fora DP. This option is signaled in the PLS2-STAT signaling by DP_TL_TYPE =‘0’ and DP_TI_LENGTH = N_(TI), while P_(I) = 1.

In each DP, the TI memory stores the input XFECBLOCKs (output XFECBLOCKsfrom the SSD/MIMO encoding block). Assume that input XFECBLOCKs aredefined as

(d_(n, s, 0, 0), d_(n, s, 0, 1), …  , d_(n, s, 0, N_(cells) − 1), d_(n, s, 1, 0), …  , d_(n, s, 1, N_(cells) − 1), …  , d_(n, s, N_(xBLOCK_n)(n, s) − 1, 0), …  , d_(n, s, N_(xBLOCK_n)(n, s)) − 1, N_(cells) − 1),

where d_(n,s,r,q) is the qth cell of the rth XFECBLOCK in the sth TIblock of the nth TI group and represents the outputs of SSD and MIMOencodings as follows.

$d_{n,s,r,q} = \{ \begin{matrix}{f_{n,s,r,q},} & {{the}\mspace{14mu} {output}\mspace{14mu} {of}\mspace{14mu} {SSD}\mspace{14mu} \ldots \mspace{14mu} {encoding}} \\{g_{n,s,r,q},} & {{the}\mspace{14mu} {output}\mspace{14mu} {of}\mspace{14mu} {MIMO}\mspace{14mu} {encoding}}\end{matrix} $

In addition, assume that output XFECBLOCKs from the time interleaver aredefined as

(h_(n, s, 0), h_(n, s, 1), …  , h_(n, s, i), …  , h_(n, s, N_(xBLOCK_n)(n, s) × N_(cells))1),

where h_(n,s,i) is the ith output cell (for i=0, . . . ,N_(xBLOCK_TI)(n,s)×N_(cells)−1) in the sth TI block of the nth TI group.

Typically, the time interleaver will also act as a buffer for DP dataprior to the process of frame building. This is achieved by means of twomemory banks for each DP. The first TI-block is written to the firstbank. The second TI-block is written to the second bank while the firstbank is being read from and so on.

The TI is a twisted row-column block interleaver. For the sth TI blockof the nth TI group, the number of rows N_(r), of a TI memory is equalto the number of cells N_(cells), i.e., N_(r)=N_(cells) while the numberof columns N_(c) is equal to the number N_(xBLOCK_TI)(n,s).

FIG. 26 illustrates the basic operation of a twisted row-column blockinterleaver according to an embodiment of the present invention.

shows a writing operation in the time interleaver and (b) shows areading operation in the time interleaver The first XFECBLOCK is writtencolumn-wise into the first column of the TI memory, and the secondXFECBLOCK is written into the next column, and so on as shown in (a).Then, in the interleaving array, cells are read out diagonal-wise.During diagonal-wise reading from the first row (rightwards along therow beginning with the left-most column) to the last row, N_(r) cellsare read out as shown in (b). In detail, assuming z_(n,s,i) (i=0, . . ., N, N_(c)) as the TI memory cell position to be read sequentially, thereading process in such an interleaving array is performed bycalculating the row index R_(n,s,i), the column index C_(n,s,i), and theassociated twisting parameter T_(n,s,i) as follows expression.

$\begin{matrix}{{{GENERATE}\mspace{14mu} ( {R_{n,s,i},C_{n,s,i}} )} = \{ {{R_{n,s,i} = {{mod}\; ( {i,N_{r}} )}},{T_{n,s,i} = {{mod}( {{S_{shift} \times R_{n,s,i}},N_{c}} )}},{C_{n,s,i} = {{mod}\; ( {{T_{n,s,i} + \lfloor \frac{i}{N_{r}} \rfloor},N_{c}} )}}} \}} & \lbrack {{Math}\mspace{14mu} {Figure}\mspace{14mu} 9} \rbrack\end{matrix}$

where S_(shift) is a common shift value for the diagonal-wise readingprocess regardless of N_(xBLOCK_TI)(n,s), and it is determined byN_(xBLOCK_TI_MAX) given in the PLS2-STAT as follows expression.

$\begin{matrix}{{for}\{ {\begin{matrix}{N_{{xBLOCK\_ TI}{\_ MAX}}^{\prime} =} & {{{if}\mspace{14mu} N_{{xBLOCK\_ TI}{\_ MAX}}\mspace{11mu} {mod}\; 2} = 0} \\{{N_{{xBLOCK\_ TI}{\_ MAX}} + 1},} & \; \\{N_{{xBLOCK\_ TI}{\_ MAX}}^{\prime} =} & {{{if}\mspace{14mu} N_{{xBLOCK\_ TI}{\_ MAX}}\mspace{11mu} {mod}\; 2} = 1} \\{N_{{xBLOCK\_ TI}{\_ MAX}},} & \;\end{matrix},{S_{shift} = \frac{N_{{xBLOCK\_ TI}{\_ MAX}}^{\prime} - 1}{2}}} } & \lbrack {{Math}\mspace{14mu} {Figure}\mspace{14mu} 10} \rbrack\end{matrix}$

As a result, the cell positions to be read are calculated by acoordinate as z_(n,s,i)=N_(r)C_(n,s,i)+R_(n,s,i).

FIG. 27 illustrates an operation of a twisted row-column blockinterleaver according to another embodiment of the present invention.

More specifically, FIG. 27 illustrates the interleaving array in the TImemory for each TI group, including virtual XFECBLOCKs whenN_(xBLOCK_TI)(0,0)=3, N_(xBLOCK_TI)(1,0)=6, N_(xBLOCK_TI)(2,0)=5.

The variable number N_(xBLOCK_TI)(n,s)=N_(r) will be less than or equalto N_(xBLOCK_TI_MAX)′. Thus, in order to achieve a single-memorydeinterleaving at the receiver side, regardless of N_(xBLOCK_TI)(n,s),the interleaving array for use in a twisted row-column block interleaveris set to the size of N_(r)×N_(c)=N_(cells)×N_(xBLOCK_TI_MAX)′ byinserting the virtual XFECBLOCKs into the TI memory and the readingprocess is accomplished as follow expression.

[Math Figure 11] p = 0; for i = 0; i < N_(cells)N′_(xBLOCK TI MAX); i =i + 1 {GENERATE(R_(n,s,j), C_(n,s,j)); V_(i) = N_(r)C_(n,s,j) +R_(n,s,j)  if V_(i) < N_(cells)N_(xBLOCK)_TI(n,s)  {   Z_(n,s,p) =V_(i); p = p + 1;   } }

The number of TI groups is set to 3. The option of time interleaver issignaled in the PLS2-STAT data by DP_TI_TYPE=‘0’, DP_FRAME_INTERVAL=‘1’,and DP_TI_LENGTH=‘1’, i.e., NTI=1, IJUMP=1, and PI=1. The number ofXFECBLOCKs, each of which has Ncells=30 cells, per TI group is signaledin the PLS2-DYN data by NxBLOCK_TI(0,0)=3, NxBLOCK_TI(1,0)=6, andNxBLOCK_TI(2,0)=5, respectively. The maximum number of XFECBLOCK issignaled in the PLS2-STAT data by NxBLOCK_Group_MAX, which leads to└N_(xBLOCK_Group_MAX)/N_(TI)┘=N_(xBLOCK_TI_MAX)=6.

FIG. 28 illustrates a diagonal-wise reading pattern of a twistedrow-column block interleaver according to an embodiment of the presentinvention.

More specifically FIG. 28 shows a diagonal-wise reading pattern fromeach interleaving array with parameters of N_(xBLOCK_TI_MAX)′=7 andSshift=(7−1)/2=3. Note that in the reading process shown as pseudocodeabove, if V_(I)≥N_(cells)N_(xBLOCK_TI)(n,s), the value of Vi is skippedand the next calculated value of Vi is used.

FIG. 29 illustrates interleaved XFECBLOCKs from each interleaving arrayaccording to an embodiment of the present invention.

FIG. 29 illustrates the interleaved XFECBLOCKs from each interleavingarray with parameters of N_(xBLOCK_TI_MAX)′=7 and Sshift=3.

FIG. 30 is a view illustrating a configuration of a broadcast receptiondevice according to an embodiment of the present invention.

A case that a broadcast reception device scans broadcast service byusing fast information will be described with reference to FIGS. 30 to57.

The broadcast reception device 100 of FIG. 30 includes a broadcastreception unit 110, an internet protocol (IP) communication unit 130,and a control unit 150.

The broadcast reception unit 110 includes a channel synchronizer 111, achannel equalizer 113, and a channel decoder 115.

The channel synchronizer 111 synchronizes a symbol frequency with atiming in order for decoding in a baseband where a broadcast signal isreceived.

The channel equalizer 113 corrects the distortion of a synchronizedbroadcast signal. In more detail, the channel equalizer 113 corrects thedistortion of a synchronized signal due to multipath and Dopplereffects.

The channel decoder 115 decodes a distortion corrected broadcast signal.In more detail, the channel decoder 115 extracts a transport frame fromthe distortion corrected broadcast signal. At this point, the channeldecoder 115 may perform forward error correction (FEC).

The IP communication unit 130 receives and transmits data throughinternet network.

The control unit 150 includes a signaling decoder 151, a transportpacket interface 153, a broadband packet interface 155, a basebandoperation control unit 157, a common protocol stack 159, a service mapdatabase 161, a service signaling channel processing buffer and parser163, an A/V processor 165, a broadcast service guide processor 167, anapplication processor 169, and a service guide database 171.

The signaling decoder 151 decodes signaling information of a broadcastsignal.

The transport packet interface 153 extracts a transport packet from abroadcast signal. At this point, the transport packet interface 153 mayextract data such as signaling information or IP datagram from theextracted transport packet.

The broadcast packet interface 155 extracts an IP packet from datareceived from internet network. At this point, the broadcast packetinterface 155 may extract signaling data or IP datagram from an IPpacket.

The baseband operation control unit 157 controls an operation relatingto receiving broadcast information from a baseband.

The common protocol stack 159 extracts audio or video from a transportpacket.

The AN processor 547 processes audio or video.

The service signaling channel processing buffer and parser 163 parsesand buffers signaling information that signals broadcast service. Inmore detail, the service signaling channel processing buffer and parser163 parses and buffers signaling information that signals broadcastservice from the IP datagram.

The service map database 165 stores a broadcast service list includinginformation on broadcast services.

The service guide processor 167 processes terrestrial broadcast serviceguide data guiding programs of terrestrial broadcast service.

The application processor 169 extracts and processes application relatedinformation from a broadcast signal.

The serviced guide database 171 stores program information of broadcastservice.

FIG. 31 is a view illustrating a transport layer of broadcast serviceaccording to an embodiment of the present invention.

A broadcast transmission device may transport broadcast service andbroadcast service related data through at least one physical layer pipe(PLP) on one frequency or a plurality of frequencies. At this point, thePLP is a series of logical data delivery paths identifiable on aphysical layer. The PLP may be also referred to as a data pipe. Onebroadcast service may include a plurality of components. At this point,each of the plurality of components may be one of audio, video, and datacomponents. Each broadcasting station may transmit encapsulatedbroadcast service by using a broadcast transmission device through onePLP or a plurality of PLPs. In more detail, a broadcasting station maytransmit a plurality of components included in one service to aplurality of PLPs through a broadcast transmission device. Additionally,a broadcasting station may transmit a plurality of components includedin one service to one PLP through a broadcast transmission device. Forexample, according to the embodiment of FIG. 31, a first broadcastingstation Broadcast #1 may transmit signaling information by using abroadcast transmission device through one PLP PLP #0. Additionally,according to the embodiment of FIG. 31, the first broadcasting stationBroadcast #1 may transmit a first component Component 1 and a secondcomponent Component 2 included in a first broadcast service by using abroadcast transmission device through a different first PLP PLP #1 andsecond PLP PLP #2. Additionally, according to the embodiment of FIG. 31,the Nth broadcasting station Broadcast # N may transmit a firstcomponent Component 1 and a second component Component 2 included in afirst broadcast service Service #1 through an Nth PLP PLP # N. At thispoint, realtime broadcast service may be encapsulated into one of theuser datagram protocol (UDP) and a protocol for realtime contentstransmission, for example, the realtime transport protocol (RTP). In thecase of non-realtime contents and non-realtime data, realtime broadcastservice may be encapsulated into a packet of at least one of IP, UDP,and a contents transmission protocol, for example, FLUTE. Therefore, aplurality of PLPs delivering a least one component may be included in atransport frame that a broadcast transmission device transmits.Accordingly, the broadcast reception device 100 may need to check all ofa plurality of PLPs to perform a broadcast service scan for obtainingbroadcast service connection information. Therefore, a broadcasttransmission method and a broadcast reception method of the broadcastreception device 100 to perform a broadcast service scan are required.

FIG. 32 is a view illustrating a broadcast transport layer according toan embodiment of the present invention.

According to the embodiment of FIG. 32, the broadcast transport frameincludes a P1 part, an L1 part, a common PLP part, an interleaved PLPpart (e.g., a scheduled & interleaved PLP's part), and an auxiliary datapart.

According to the embodiment of FIG. 32, the broadcast transmissiondevice transmits information on transport signal detection through theP1 part of the transport frame. Additionally, the broadcast transmissiondevice may transmit tuning information on broadcast signal tuningthrough the P1 part.

According to the embodiment of FIG. 32, the broadcast transmissiondevice transmits a configuration of the broadcast transmission frame andcharacteristics of each PLP through the L1 part. At this point, thebroadcast reception device 100 decodes the L1 part on the basis of theP1 part to obtain the configuration of the broadcast transport frame andthe characteristics of each PLP.

According to the embodiment of FIG. 32, the broadcast transmissiondevice may transmit information commonly applied to PLPs through thecommon PLP part. According to a specific embodiment, the broadcasttransport frame may not include the common PLP part.

According to the embodiment of FIG. 32, the broadcast transmissiondevice transmits a plurality of components included in broadcast servicethrough an interleaved PLP part. At this point, the interleaved PLP partincludes a plurality of PLPs.

Moreover, according to the embodiment of FIG. 32, the broadcasttransmission device may signal to which PLP components configuring eachbroadcast service are transmitted through an L1 part or a common PLPpart. However, the broadcast reception device 100 decodes all of aplurality of PLPs of an interleaved PLP part in order to obtain specificbroadcast service information on broadcast service scan.

Unlike the embodiment of FIG. 32, the broadcast transmission device maytransmit a broadcast transport frame including a broadcast servicetransmitted through a broadcast transport frame and an additional partthat includes information on a component included in the broadcastservice. At this point, the broadcast reception device 100 may instantlyobtain information on the broadcast service and the components thereinthrough the additional part. This will be described with reference toFIGS. 33 to 45.

FIG. 33 is a view of a broadcast transport frame according to anotherembodiment of the present invention.

According to the embodiment of FIG. 33, the broadcast transport frameincludes a P1 part, an L1 part, a fast information channel (FIC) part,an interleaved PLP part (e.g., a scheduled & interleaved PLP's part),and an auxiliary data part.

Except the L1 part and the FIC part, other parts are identical to thoseof FIG. 32.

The broadcast transmission device transmits fast information through theFIC part. The fast information may include configuration information ofa broadcast stream transmitted through a transport frame, simplebroadcast service information, and component information. The broadcastreception device 100 may scan broadcast service on the basis of the FICpart. In more detail, the broadcast reception device 100 may extractinformation on broadcast service from the FIC part.

The L1 part may further include version information of fast informationrepresenting whether fast information in the FIC part changes. When thefast information is changed, the broadcast transmission device maychange the version information of the fast information. Additionally,the broadcast reception device 100 may determine whether the fastinformation is received on the basis of the version information of thefast information. In more detail, when the version information of thepreviously received fast information is identical to the versioninformation of the fast information of the L1 part, the broadcastreception device 100 may not receive the fast information.

Information in the FIC part will be described in more detail withreference to FIG. 34.

FIG. 34 illustrates a syntax of a fast information chunk according to anembodiment of the present invention.

The fast information chunk transmitted through the FIC part of abroadcast transport frame includes at least one of an FIT_data_versionfield, a num_broadcast field, a broadcast_id field, a delivery_system_idfield, a num_service field, a service_id field, a service_categoryfield, a service_hidden_flag field, and an SP_indicator field.

The FIT_data_version field represents version information on the syntaxand semantics of a fast information chunk. The broadcast receptiondevice 100 may determine whether to process a corresponding fastinformation chunk by using the above. For example, when a value of theFIT_data_version field represents a version that the broadcast receptiondevice 100 does not support, the broadcast reception device 100 may notprocess a fast information chunk. According to a specific embodiment ofthe present invention, the FIT_data_version field may be an 8-bit field.

The num_broadcast field represents the number of broadcasting stationstransmitting broadcast services through a corresponding frequency or atransmitted transport frame. According to a specific embodiment of thepresent invention, the num_broadcast field may be an 8-bit field.

The broadcast_id field represents an identifier indentifying abroadcasting station transmitting broadcast service through acorresponding frequency or transport frame. When the broadcasttransmission device transmits MPEG-2 TS based data, broadcast_id mayhave the same value as transport_stream_id of MPEG-2 TS. According to aspecific embodiment of the present invention, the broadcast_id field maybe a 16-bit field.

The delivery_system_id field represents an identifier identifying abroadcast transmission system by applying the same transmissionparameter on a broadcast network and processing it. According to aspecific embodiment of the present invention, the delivery_system_idfield may be a 16-bit field.

The num_service field represents the number of broadcast services that abroadcasting station corresponding to broadcast_id transmits in acorresponding frequency or transport frame. According to a specificembodiment of the present invention, the num_service field may be an8-bit field.

The service_id field represents an identifier indentifying broadcastservice. According to a specific embodiment of the present invention,the service_id field may be a 16-bit field.

The service_category field represents a category of broadcast service.In more detail, the service_category field may represent at least one ofTV service, radio service, broadcast service guide, RI service, andemergency alerting. For example, in the case of a value of theservice_category field is 0x01, it represents TV service. In the case ofa value of the service_category field is 0x02, it represents radioservice. In the case of a value of the service_category field is 0x03,it represents RI service. In the case of a value of the service_categoryfield is 0x08, it represents service guide. In the case of a value ofthe service_category field is 0x09, it represents emergency alerting.According to a specific embodiment of the present invention, theservice_category field may be a 6-bit field.

The service_hidden_flag field represents whether a correspondingbroadcast service is hidden service. If the broadcast service is thehidden service, it is test service or special service. Accordingly, ifthe corresponding service is the hidden service, the broadcast receptiondevice 100 may not display the corresponding service in a service guideor service list. Moreover, when the corresponding service is the hiddenservice, the broadcast reception device 100 may allow the correspondingservice not to be selected by a channel up/down key input and thecorresponding service to be selected by a number key input. According toa specific embodiment of the present invention, the service_hidden_flagmay be a 1-bit field.

The SP_indicator field may represent whether service protection isapplied to at least one component in the corresponding broadcastservice. For example, when a value of SP_indicator is 1, it mayrepresent that service protection is applied to at least one componentin the corresponding broadcast service. According to a specificembodiment of the present invention, the SP_indicator field may be a1-bit field. A broadcast service transmitting method and a broadcastservice receiving method using a fast information chunk will bedescribed with reference to FIGS. 35 and 36.

FIG. 35 is a view when a broadcast transmission device transmitsbroadcast service according to an embodiment of the present invention.

The broadcast transmission device obtains information of a broadcastservice to be transmitted through a control unit in operation S101. Inmore detail, the broadcast transmission device obtains information of abroadcast service to be included in one frequency or transport frame.According to a specific embodiment of the present invention, thebroadcast transmission device may obtain at least one of a broadcastingstation identifier identifying a broadcasting station that transmits abroadcast, a delivery system delivering a broadcast, an identifieridentifying broadcast service, category information of broadcastservice, information representing whether it is hidden service, andinformation representing whether service protection is applied to acomponent of broadcast service.

The broadcast transmission device generates fast information on thebasis of broadcast service information through a control unit inoperation S103. At this point, the fast information may include at leastone of a broadcasting station identifier identifying a broadcastingstation transmitting a broadcast, a delivery system identifieridentifying a delivery system delivering a broadcast, an identifieridentifying broadcast service, category information of broadcastservice, information representing whether it is hidden service,information on whether service protection is applied to a component ofbroadcast service, information representing the number of broadcastingstations transmitting broadcast services in a transport frame where fastinformation is to be inserted, and information representing the numberof broadcast services corresponding to each broadcasting stationidentifier in a transport frame. According to a specific embodiment ofthe present invention, the broadcast transmission device may generate afast information chunk as shown in the embodiment of FIG. 34.

The broadcast transmission device inserts fast information into a fastinformation channel part of a transport frame through a control unit inoperation S105. The broadcast transmission device may insert fastinformation into a fast information channel part of a transport frame asshown in the embodiment of FIG. 33.

The broadcast transmission device transmits a broadcast signal includinga transport frame through a transmission unit in operation S107.

FIG. 36 is a view when a broadcast reception device receives broadcastservice according to an embodiment of the present invention.

The broadcast reception device 100 tunes a channel for receivingbroadcast signal through a broadcast reception unit 110 in operationS301. In general, in the case of terrestrial broadcast, a channel listincluding information of a frequency for transmitting broadcast servicefor each region and a specific transmission parameter is defined.Additionally, in the case of cable broadcast, a channel list includinginformation of a frequency for transmitting broadcast service for eachcable broadcast operator and a specific transmission parameter isdefined. Therefore, according to a specific embodiment of the presentinvention, the broadcast reception device 100 may tune a channel forreceiving broadcast signal on the basis of a predetermined channel list.

The broadcast reception device 100 obtains fast information through thecontrol unit 150 in operation S303. In more detail, the broadcastreception device 100 may extract fast information from the FIC part of atransport frame. At this point, the fast information may be the fastinformation chunk of FIG. 34.

When there is a broadcast service in a transport frame, the broadcastreception device 100 obtains broadcast service connection informationthrough the control unit 150 in operations S305 and S307. Additionally,the broadcast reception device 100 may determine whether there is abroadcast service in a transport frame on the basis of informationrepresenting the number of broadcasting stations transmitting abroadcast service in a transport frame. According to another specificembodiment of the present invention, the broadcast reception device 100may determine whether there is a broadcast service in a transport frameon the basis of whether there is a broadcast service corresponding toeach broadcasting station identifier in a transport frame.

The broadcast service connection information may be minimum informationnecessary for receiving broadcast service. In more detail, the broadcastservice connection information may include at least one of abroadcasting station identifier identifying a broadcasting stationtransmitting a broadcast, a delivery system identifier identifying adelivery system delivering a broadcast, an identifier identifyingbroadcast service, category information of broadcast service,information representing whether it is hidden service, information onwhether service protection is applied to a component of broadcastservice, information representing the number of broadcasting stationstransmitting broadcast services in a transport frame where fastinformation is to be inserted, and information representing the numberof broadcast services corresponding to each broadcasting stationidentifier in a transport frame. According to a specific embodiment ofthe present invention, the broadcast reception device 100 may generate abroadcast service list including connection information on a pluralityof broadcast services on the basis of the obtained broadcast serviceconnection information.

When all broadcast service connection information in fast information isnot obtained, the broadcast reception device 100 obtains broadcastservice connection information of the next broadcast service inoperations S309 and S311. According to a specific embodiment of thepresent invention, the fast information may include broadcast serviceconnection information on a plurality of broadcast services. At thispoint, the fast information may include broadcast service connectioninformation in loop form in which broadcast service connectioninformation on a plurality of broadcast services is sequentially stored.In more detail, the fast information may include broadcast serviceconnection information on a broadcast service that each broadcastingstation services in loop form.

When there is no broadcast service in a transport frame or all broadcastservice connection information in fast information is obtained, thebroadcast reception device 100 determines whether a currently tunedchannel is the last channel in operations S305, S309, and S313. In moredetail, the broadcast reception device 100 determines whether acurrently tuned channel is the last channel of the above-describedpredetermined channel list.

If the currently tuned channel is not the last channel, the broadcastreception device 100 obtains fast information by tuning the next channelin operation S315.

If the currently tuned channel is the last channel, the broadcastreception device 100 receives broadcast service in operation S317. Atthis point, a broadcast service that the broadcast reception device 100receives may be a pre-set broadcast service. According to anotherspecific embodiment of the present invention, a broadcast service thatthe broadcast reception device 100 receives may be a broadcast serviceobtaining the connection information lastly. According to anotherspecific embodiment of the present invention, a broadcast service thatthe broadcast reception device 100 receives may be a broadcast serviceobtaining the connection information firstly. However, according to theembodiments of FIGS. 33 to 35, the broadcast reception device 100 mayobtain only simple information on a broadcasting station in acorresponding frequency or transport frame and a broadcast service of acorresponding broadcasting station. Accordingly, in order to obtainspecific information on each broadcast service transmitted in acorresponding frequency or transport frame, the broadcast receptiondevice 100 needs to perform an additional operation. For example, inorder to obtain information on a component configuring each broadcastservice, the broadcast reception device 100 needs to extract signalinginformation in an interleaved PLP part in a transport frame. Therefore,a new broadcast transmission device, operation method thereof, broadcastreception device, and operation method thereof are required to allow thebroadcast reception device 100 to quickly and efficiently obtainspecific information on a broadcast service in a transport frame. Thiswill be described with reference to FIGS. 37 to 48.

When a transport frame includes an additional PLP part includingspecific information on broadcast services transmitted through atransport frame in an interleaved PLP part, the broadcast receptiondevice 100 may obtain specific information on broadcast servicestransmitted through a transport frame by extracting only an additionalPLP part. Moreover, when a fast information chunk includes informationof an additional PLP part including specific information on broadcastservices transmitted through a transport frame, the broadcast receptiondevice 100 may efficiently obtain information of an additional PLP partincluding specific information on broadcast services transmitted througha transport frame. Accordingly, a transport frame may include anadditional PLP part including specific information on broadcast servicestransmitted through a transport frame in an interleaved PLP part. Atthis point, an additional PLP part including specific information onbroadcast services transmitted through a transport frame may includesignaling information signaling broadcast service. According to anotherspecific embodiment, an additional PLP part including specificinformation on broadcast services transmitted through a transport framemay include a component included in broadcast service.

Moreover, a fast information chunk may include information on anadditional PLP part including specific information on broadcast servicestransmitted through a transport frame. In more detail, the fastinformation chunk may include an identifier identifying an additionalPLP part including specific information on broadcast servicestransmitted through a transport frame. This will be described in moredetail with reference to FIGS. 37 to 40. Hereinafter, an additional PLPpart including specific information on broadcast services transmittedthrough a transport frame is referred to as a base PLP.

FIGS. 37 to 40 illustrate a syntax of a fast information chunk accordingto another embodiment of the present invention.

According to the embodiment of FIG. 37, unlike the embodiment of FIG.34, the fast information chunk further includes a base_PLP_id field anda base_PLP_version field.

The base_PLP_id field is an identifier identifying a base PLP forbroadcast service of a broadcasting station corresponding tobroadcast_id. According to a specific embodiment of the presentinvention, a base PLP may deliver signaling information signaling abroadcast service transmitted through a transport frame. At this point,according to a specific embodiment of the present invention, signalinginformation signaling broadcast service may be PSI of MPEG2-TS standard.Additionally, according to a specific embodiment of the presentinvention, signaling information signaling broadcast service may be PSIPof ATSC standard. Additionally, according to a specific embodiment ofthe present invention, signaling information signaling broadcast servicemay be SI of DVB standard. According to another specific embodiment ofthe present invention, a base PLP may include a component included in abroadcast service transmitted through a transport frame. According to aspecific embodiment of the present invention, the base_PLP_id field maybe an 8-bit field.

The base_PLP_version field may represent version information on a changein data transmitted through a base PLP. For example, when signalinginformation is delivered through a base PLP, if there is a change inservice signaling, a value of the base_PLP_version field may beincreased by 1. According to a specific embodiment of the presentinvention, the base_PLP_version field may be a 5-bit field. Thebroadcast reception device 100 may determine whether to receive datatransmitted through a base PLP on the basis of the base_PLP_versionfield. For example, when a value of the base_PLP_version field isidentical to a value of the base_PLP_version field transmitted through apreviously received base PLP, the broadcast reception device 100 may notreceive data transmitted through a base PLP.

However, the number of PLPs in a transport frame may be set to themaximum 32. In such a case, since the maximum value for the base_PLP_idfield is less than 32, the base_PLP_id field may be a 6-bit field.Additionally, since a value that the num_service field has is less than32, the num_service field may be a 5-bit field.

FIG. 38 is a view when the base_PLP_id field is a 6-bit field and thenum_service field is a 5-bit field.

Additionally, a fast information chunk may include information on acomponent of broadcast service. According to a specific embodiment ofthe present invention, a fast information chunk may include anum_component field, a component_id field, and a PLP_id field.

The num_component field represents the number of components configuringa corresponding broadcast service. According to a specific embodiment ofthe present invention, the num_component field may be an 8-bit field.

The component_id field represents an identifier identifying acorresponding component in broadcast service. According to a specificembodiment of the present invention, the component_id field may be an8-bit field.

The PLP_id field represents an identifier identifying a PLP where acorresponding component is transmitted in a transport frame. Accordingto a specific embodiment of the present invention, the PLP_id field maybe an 8-bit field.

FIG. 39 is a view when a fast information chunk includes a num_componentfield, a component_id field, and a PLP_id field.

Additionally, as described above, the number of PLPs in a transportframe may be set to the maximum 32. In such a case, when a fastinformation chunk includes a num_component field, a component_id field,and a PLP_id field, the base_PLP_id field may be a 6-bit field.Additionally, the num_service field may be a 5-bit field.

FIG. 40 is a view when a fast information chunk includes a num_componentfield, a component_id field, and a PLP_id field, a base_PLP_id field isa 6-bit field, and a num_service field is a 5-bit field.

FIG. 41 is a view when a broadcast transmission device transmitsbroadcast service according to another embodiment of the presentinvention.

The broadcast transmission device obtains information of a broadcastservice to be transmitted through a control unit in operation S501. Inmore detail, the broadcast transmission device obtains information of abroadcast service to be included in one frequency or transport frame.According to a specific embodiment of the present invention, thebroadcast transmission device may obtain at least one of a broadcastingstation identifier identifying a broadcasting station that transmits abroadcast, a delivery system delivering a broadcast, an identifieridentifying broadcast service, category information of broadcastservice, information representing whether it is hidden service,information representing whether service protection is applied to acomponent of broadcast service, and signaling information signalingbroadcast service. At this point, the signaling information may be oneof PSI of MPEG2-TS standard, PSIP of ATSC standard, and SI of DVBstandard. Additionally, the signaling information may include signalinginformation signaling broadcast service on a newly established standardbesides the above-mentioned standards.

The broadcast transmission device inserts specific information onbroadcast services transmitted through a transport frame into at leastone PLP in an interleaved PLP part through a control unit in operationS503 on the basis of broadcast service information. As described above,specific information on broadcast services may be signaling informationsignaling broadcast service. At this point, the signaling informationmay be one of PSI of MPEG2-TS standard, PSIP of ATSC standard, and SI ofDVB standard. Additionally, the signaling information may includesignaling information signaling broadcast service on a newly establishedstandard besides the above-mentioned standards. Additionally, acomponent of a broadcast service among broadcast services transmittedthrough a transport frame may be inserted into at least one PLP in aninterleaved PLP part on the basis of broadcast service information. Atthis point, a PLP including specific information on broadcast servicestransmitted through a transport frame is a base PLP.

The broadcast transmission device generates fast information through acontrol unit on the basis of a PLP including broadcast serviceinformation and specific information on broadcast services in operationS505. At this point, the fast information may include at least one of abroadcasting station identifier identifying a broadcasting stationtransmitting a broadcast, a delivery system identifier identifying adelivery system delivering a broadcast, an identifier identifyingbroadcast service, category information of broadcast service,information representing whether it is hidden service, information onwhether service protection is applied to a component of broadcastservice, information representing the number of broadcasting stationstransmitting broadcast services in a transport frame where fastinformation is to be inserted, information representing the number ofbroadcast services corresponding to each broadcasting station identifierin a transport frame, information representing the number of componentsincluded in broadcast service, an identifier identifying a componentincluded in broadcast service, and an identifier identifying a PLPincluding a corresponding component. Additionally, the fast informationincludes information on a base PLP. In more detail, the fast informationmay include an identifier identifying a base PLP. Additionally, the fastinformation may include information representing an information changein a base PLP. According to a specific embodiment of the presentinvention, the broadcast transmission device may generate a fastinformation chunk as shown in the embodiment of FIGS. 37 to 40.

The broadcast transmission device inserts the fast information into afast information channel part of a transport frame through a controlunit in operation S507. The broadcast transmission device may insertfast information into a fast information channel part of a transportframe as shown in the embodiment of FIG. 33.

The broadcast transmission device transmits a broadcast signal includinga transport frame through a transmission unit in operation S509.

FIG. 42 is a view when a broadcast reception device scans broadcastservice according to another embodiment of the present invention.

The broadcast reception device 100 tunes a channel for receivingbroadcast signal through a broadcast reception unit 110 in operationS701. As described above, in general, in the case of terrestrialbroadcast, a channel list including information of a frequency fortransmitting broadcast service to each region and a specifictransmission parameter is defined. Additionally, in the case of cablebroadcast, a channel list including information of a frequency fortransmitting broadcast service for each cable broadcast operator and aspecific transmission parameter is defined. Therefore, according to aspecific embodiment of the present invention, the broadcast receptiondevice 100 may tune a channel for receiving broadcast signal on thebasis of a predetermined channel list.

The broadcast reception device 100 obtains fast information through thecontrol unit 150 in operation S703. In more detail, the broadcastreception device 100 may extract fast information from the FIC part of atransport frame. At this point, the fast information may be the fastinformation chunk in the embodiment of FIGS. 37 to 40.

When there is a broadcast service in a transport frame, the broadcastreception device 100 obtains base PLP information and broadcast serviceconnection information through the control unit 150 in operations S705and S707. Additionally, the broadcast reception device 100 may determinewhether there is a broadcast service in a transport frame on the basisof information representing whether the number of broadcasting stationstransmitting a broadcast service in a transport frame. According toanother specific embodiment, the broadcast reception device 100 maydetermine whether there is a broadcast service in a transport frame onthe basis of information representing whether there is a broadcastservice corresponding to each broadcasting station identifier in atransport frame.

The broadcast service connection information may be minimum informationnecessary for receiving broadcast service. In more detail, the broadcastservice connection information may include at least one of abroadcasting station identifier identifying a broadcasting stationtransmitting a broadcast, a delivery system identifier identifying adelivery system delivering a broadcast, an identifier identifyingbroadcast service, category information of broadcast service,information representing whether it is hidden service, information onwhether service protection is applied to a component of broadcastservice, information representing the number of broadcasting stationstransmitting broadcast services in a transport frame where fastinformation is to be inserted, information representing the number ofbroadcast services corresponding to each broadcasting station identifierin a transport frame, information representing the number of componentsincluded in broadcast service, an identifier identifying a componentincluded in broadcast service, and an identifier identifying a PLPincluding a corresponding component. According to a specific embodimentof the present invention, the broadcast reception device 100 maygenerate a broadcast service list including connection information on aplurality of broadcast services on the basis of the obtained broadcastservice connection information. The base PLP information may include atleast one of an identifier identifying a base PLP and informationrepresenting an information change in a base PLP.

The broadcast reception device 100 obtains signaling information on abroadcast service on the basis of the base PLP information through thecontrol unit 150. As described above, the signaling information may beone of PSI of MPEG2-TS standard, PSIP of ATSC standard, and SI of DVBstandard. Additionally, the signaling information may include signalinginformation signaling broadcast service on a newly established standardbesides the above-mentioned standards.

At this point, specific operations of the broadcast reception device 100will be described with reference to FIGS. 43 and 44.

As shown in the embodiment of FIG. 43, the broadcast reception device100 may obtain broadcast service connection information from fastinformation. Additionally, the broadcast reception device 100 maygenerate a broadcast service list including connection information onbroadcast service on the basis of the broadcast service connectioninformation. However, in order to allow the broadcast reception device100 to obtain specific information on broadcast service, informationneeds to be obtained from a base PLP. For this, the broadcast receptiondevice 100 identifies a base PLP on the basis of base PLP information.In more detail, like the embodiment of FIG. 44, the broadcast receptiondevice 100 may obtain a base PLP identifier from the fast informationand may identify a base PLP from a plurality of PLPs on the basis of thebase PLP identifier. Additionally, the broadcast reception device 100may obtain signaling information in the base PLP on the basis of thebroadcast service connection information. In more detail, the broadcastreception device 100 may obtain signaling information corresponding tothe broadcast service connection information. For example, the broadcastreception device 100 may obtain from the base PLP the type of acomponent included in a broadcast service corresponding to the broadcastservice identifier obtained from the fast information.

When all broadcast service connection information in the fastinformation is not obtained, the broadcast reception device 100 obtainsbroadcast service connection information of the next broadcast servicein operations S711 and S713. According to a specific embodiment of thepresent invention, the fast information may include broadcast serviceconnection information on a plurality of broadcast services. At thispoint, the fast information may include broadcast service connectioninformation in loop form in which broadcast service connectioninformation on a plurality of broadcast services is sequentially stored.In more detail, the fast information may include broadcast serviceconnection information on a broadcast service that each broadcastingstation services in loop form.

When there is no broadcast service in a transport frame or all broadcastservice connection information in the fast information is obtained, thebroadcast reception device 100 determines whether a currently tunedchannel is the last channel in operations S705, S711, and S715. In moredetail, the broadcast reception device 100 determines whether acurrently tuned channel is the last channel of the above-describedpredetermined channel list.

If the currently tuned channel is not the last channel, the broadcastreception device 100 tunes the next channel to obtain the fastinformation in operation S717.

If the currently tuned channel is the last channel, the broadcastreception device 100 receives broadcast service in operation S719. Atthis point, a broadcast service that the broadcast reception device 100receives may be a pre-set broadcast service. According to anotherspecific embodiment of the present invention, a broadcast service thatthe broadcast reception device 100 receives may be a broadcast serviceobtaining the connection information lastly. According to anotherspecific embodiment of the present invention, a broadcast service thatthe broadcast reception device 100 receives may be a broadcast serviceobtaining the connection information firstly.

The broadcast reception device 100 may efficiently obtain specificinformation on broadcast service in addition to simple information onbroadcast service through a base PLP. Additionally, the broadcastreception device 100 may instantly obtain specific information onbroadcast service in addition to simple information on broadcast servicethrough a base PLP.

However, if there is no additional FIC part in a transport frame, thebroadcast transmission device may transmit fast information in a tableformat through a common PLP part delivering information shared in a PLPor an additional PLP. At this point, at this point, the fast informationtable may be encapsulated into a generic packet including MPEG2-TS,IP/UDP datagram, or IP/UDP datagram. Additionally, the broadcastreception device 100 may receive a fast information table from a commonPLP part or an additional PLP through the control unit 150.Additionally, the broadcast reception device 100 may perform anoperation of FIG. 44 on a fast information table. The format of a fastinformation table will be described with reference to FIGS. 45 to 48.

FIG. 45 illustrates a syntax of a fast information table according to anembodiment of the present invention.

The fast information table may include at least one of a table_id field,a section_syntax_indicator field, a private_indicator field, asection_length field, a table_id_extension field, a table_id_extensionfield, a FIT_data_version field, a current_next_indicator field, asection_number field, a last_section_number field, a num_broadcastfield, a broadcast_id field, a delivery_system_id field, a base_PLP_idfield, a base_PLP_version field, num_service field, a service_id field,a service_category field, a service_hidden_flag field, a SP_indicatorfield, a num_component field, a component_id field, and a PLP_id field.

The table_id field represents an identifier of a fast information table.At this point, the table_id may be 0xFA, that is, one of reserved idvalues defined in ATSC A/65. According to a specific embodiment of thepresent invention, the table_id field may be an 8-bit field.

The section_syntax_indicator field represents whether a fast informationtable is a private section table in the long formant of MEPG-2 TSstandard. According to a specific embodiment of the present invention,the section_syntax_indicator may be a 1-bit field.

The private_indicator field represents whether a current tablecorresponds to a private section. According to a specific embodiment ofthe present invention, the private_indicator field may be a 1-bit field.

The section_length field represents the length of a section includedfollowing the section_length field. According to a specific embodimentof the present invention, the section_length field may be a 12-bitfield.

The table_id_extension field represents an identifier identifying fastinformation. According to a specific embodiment of the presentinvention, the table_id_extension field may be a 16-bit field.

The FIT_data_version field represents version information on the syntaxand semantics of a fast information table. The broadcast receptiondevice 100 may determine whether to process a corresponding fastinformation table by using the FIT_data_version field. For example, whena value of the FIT_data_version field represents a version that thebroadcast reception device 100 does not support, the broadcast receptiondevice 100 may not process a fast information table. According to aspecific embodiment of the present invention, the FIT_data_version fieldmay be a 5-bit field.

The current_next_indicator field represents whether information of afast information table is currently available. In more detail, when avalue of the current_next_indicator field is 1, thecurrent_next_indicator field may represent that information of a fastinformation table is available. Moreover, when a value of thecurrent_next_indicator field is 1, information of a fast informationtable is available for the next time. According to a specific embodimentof the present invention, the current_next_indicator field may be a1-bit field.

The section_number field represents a current section number. Accordingto a specific embodiment of the present invention, the section_numberfield may be an 8-bit field.

The last_section_number field represents the last section number. Whenthe size of a fast information table is large, the fast informationtable may be divided into a plurality of sections and then transmitted.At this point, the broadcast reception device 100 determines whether allsections necessary for a fast information table are received on thebasis of the section_number field and the last_section_number field.According to a specific embodiment of the present invention, thelast_section_number field may be an 8-bit field.

The num_broadcast field represents the number of broadcasting stationstransmitting broadcast services through a corresponding frequency or atransmitted transport frame. According to a specific embodiment of thepresent invention, the num_broadcast field may be an 8-bit field.

The broadcast_id field represents an identifier indentifying abroadcasting station transmitting broadcast service through acorresponding frequency or transport frame. When the broadcasttransmission device transmits MPEG-2 TS based data, broadcast_id mayhave the same value as transport_stream_id of MPEG-2 TS. According to aspecific embodiment of the present invention, the broadcast_id field maybe a 16-bit field.

The delivery_system_id field represents an identifier identifying abroadcast transmission system by applying the same transmissionparameter on a broadcast network and processing it. According to aspecific embodiment of the present invention, the delivery_system_idfield may be a 16-bit field.

The base_PLP_id field is an identifier identifying a base PLP forbroadcast service of a broadcasting station corresponding tobroadcast_id. According to a specific embodiment of the presentinvention, a base PLP may deliver signaling information signaling abroadcast service transmitted through a transport frame. At this point,according to a specific embodiment of the present invention, signalinginformation signaling broadcast service may be PSI of MPEG2-TS standard.Additionally, according to a specific embodiment of the presentinvention, signaling information signaling broadcast service may be PSIPof ATSC standard. Additionally, according to a specific embodiment ofthe present invention, signaling information signaling broadcast servicemay be SI of DVB standard. According to another specific embodiment ofthe present invention, a base PLP may include a component included in abroadcast service transmitted through a transport frame. According to aspecific embodiment of the present invention, the base_PLP_id field maybe an 8-bit field.

The base_PLP_version field may represent version information on a changein data transmitted through a base PLP. For example, when signalinginformation is delivered through a base PLP, if there is a change inservice signaling, a value of the base_PLP_version field may beincreased by 1. According to a specific embodiment of the presentinvention, the base_PLP_version field may be a 5-bit field.

The num_service field represents the number of broadcast services that abroadcasting station corresponding to broadcast_id transmits in acorresponding frequency or transport frame. According to a specificembodiment of the present invention, the num_service field may be an8-bit field.

The service_id field represents an identifier indentifying broadcastservice. According to a specific embodiment of the present invention,the service_id field may be a 16-bit field.

The service_category field represents a category of broadcast service.In more detail, the service_category field may represent at least one ofTV service, radio service, broadcast service guide, RI service, andemergency alerting. For example, in the case of a value of theservice_category field is 0x01, it represents TV service. In the case ofa value of the service_category field is 0x02, it represents radioservice. In the case of a value of the service_category field is 0x03,it represents RI service. In the case of a value of the service_categoryfield is 0x08, it represents service guide. In the case of a value ofthe service_category field is 0x09, it represents emergency alerting.According to a specific embodiment of the present invention, theservice_category field may be a 6-bit field.

The service_hidden_flag field represents whether a correspondingbroadcast service is hidden service. If the broadcast service is thehidden service, it is test service or special service. Accordingly, ifthe corresponding service is the hidden service, the broadcast receptiondevice 100 may not display the corresponding service in a service guideor service list. Moreover, when the corresponding service is the hiddenservice, the broadcast reception device 100 may allow the correspondingservice not to be selected by a channel up/down key input and thecorresponding service to be selected by a number key input. According toa specific embodiment of the present invention, the service_hidden_flagmay be a 1-bit field.

The SP_indicator field may represent whether service protection isapplied to at least one component in the corresponding broadcastservice. For example, when a value of SP_indicator is 1, it mayrepresent that service protection is applied to at least one componentin the corresponding broadcast service. According to a specificembodiment of the present invention, the SP_indicator field may be a1-bit field.

The num_component field represents the number of components configuringa corresponding broadcast service. According to a specific embodiment ofthe present invention, the num_component field may be an 8-bit field.

The component_id field represents an identifier identifying acorresponding component in broadcast service. According to a specificembodiment of the present invention, the component_id field may be an8-bit field.

The PLP_id field represents an identifier identifying a PLP where acorresponding component is transmitted in a transport frame. Accordingto a specific embodiment of the present invention, the PLP_id field maybe an 8-bit field. The contents of information in a fast informationtable are similar to the contents of the above-described fastinformation chunk. However, in the case of a fast information table,since information is not transmitted through an FIC channel part, thesize of information in a fast information table is less limited thanthat of fast information chunk. Accordingly, the fast information tablemay include other information that a fast information chunk does notinclude. This will be described with reference to FIG. 46.

FIG. 46 illustrates a syntax of a fast information table according toanother embodiment of the present invention.

As shown in an embodiment of FIG. 46, a fast information table mayinclude at least one of a short_service_name_length field, ashoert_service_name field, a num_desciptors field, and aservice_descriptor field.

The short_service_name_length field represents the length of a value ofthe shoert_service_name field. According to a specific embodiment of thepresent invention, the short_service_name_length field may be a 3-bitfield.

The shoert_service_name field represents a short name of a correspondingbroadcast service. According to a specific embodiment of the presentinvention, the short_service_name field may be a field having a bit sizevalue obtained by multiplying a value of the short_service_name_lengthfield by 8.

The num_desciptors field represents the number of descriptors in servicelevel including specific information of a corresponding service.According to a specific embodiment of the present invention, thenum_desciptors field may be an 8-bit field.

The service_descriptor field represents a service descriptor includingspecific information of a corresponding service. As described above, inthe case of a fast information table, since it is less limited than afast information chunk, specific information on broadcast service may betransmitted and received together through service_descriptor.Additionally, the fast information table may be transmitted and receivedin an XML file format in addition to the bit stream format describedthrough FIGS. 45 and 48. This will be described with reference to FIG.47.

FIG. 47 illustrates a syntax of a fast information table according toanother embodiment of the present invention.

A fast information table in an XML format may include at least one of aFITdataversion attribute, a broadcastID attribute, a deliverySystemIDattribute, a basePLPID attribute, a basePLPversion attribute, aserviceID attribute, a serviceCategory attribute, a serviceHiddenattribute, a ServiceProtection attribute, a componentID attribute, and aPLPID attribute.

The FITdataversion attribute represents version information on a syntaxand semantics of a fast information table. The broadcast receptiondevice 100 may determine whether to process a corresponding fastinformation chunk by using the above. For example, when a value of theFITdataversion attribute represents a version that the broadcastreception device 100 does not support, the broadcast reception device100 may not process a fast information table.

The broadcastID attribute represents an identifier identifying abroadcasting station transmitting broadcast service through acorresponding frequency of transport frame. When the broadcasttransmission device transmits MPEG-2 TS based data, the broadcastIDattribute may have the same value as transport_stream_id of MPEG-2 TS.

The deliverySystemID attribute represents an identifier identifying abroadcast transmission system applying the same transmission parameterand processing it on a broadcast network.

The basePLPID attribute is an identifier identifying a base PLP for abroadcast service of a broadcasting station corresponding to thebroadcastID attribute. According to a specific embodiment of the presentinvention, a base PLP may deliver signaling information signaling abroadcast service transmitted through a transport frame. At this point,according to a specific embodiment of the present invention, signalinginformation signaling broadcast service may be PSI of MPEG2-TS standard.Additionally, according to a specific embodiment of the presentinvention, signaling information signaling broadcast service may be PSIPof ATSC standard. Additionally, according to a specific embodiment ofthe present invention, signaling information signaling broadcast servicemay be SI of DVB standard. According to another specific embodiment ofthe present invention, a base PLP may include a component included in abroadcast service transmitted through a transport frame.

The basePLPversion attribute may represent version information on achange in data transmitted through a base PLP. For example, whensignaling information is delivered through a base PLP, if there is achange in service signaling, a value of the base_PLP_version field maybe increased by 1.

The serviceID attribute represents an identifier identifying broadcastservice.

The serviceCategory attribute represents a category of broadcastservice. In more detail, the service_category field may represent atleast one of TV service, radio service, broadcast service guide, RIservice, and emergency alerting. For example, in the case of a value ofthe serviceCategory attribute is 0x01, it represents TV service. In thecase of a value of the serviceCategory attribute is 0x02, it representsradio service. In the case of a value of the serviceCategory attributeis 0x03, it represents RI service. In the case of a value of theserviceCategory attribute is 0x08, it represents service guide. In thecase of a value of the serviceCategory attribute is 0x09, it representsemergency alerting.

The serviceHidden attribute represents whether a corresponding broadcastservice is hidden service. If the broadcast service is the hiddenservice, it is test service or special service. Accordingly, if thecorresponding service is the hidden service, the broadcast receptiondevice 100 may not display the corresponding service in a service guideor service list. Moreover, when the corresponding service is the hiddenservice, the broadcast reception device 100 may allow the correspondingservice not to be selected by a channel up/down key input and thecorresponding service to be selected by a number key input.

The ServiceProtection attribute may represent whether service protectionis applied to at least one component in a corresponding broadcastservice. For example, when a value of the ServiceProtection attribute is1, it may represent that service protection is applied to at least onecomponent in a corresponding broadcast service.

The componentID attribute represents an identifier identifying acorresponding component in broadcast service.

The PLPID attribute represents an identifier identifying a PLP where acorresponding component is transmitted in a transport frame.

The broadcast transmission device may transmit a fast information tablein an XML format through an internet network in addition to a broadcastnetwork. In more detail, the broadcast reception device 100 may requesta fast information table for specific frequency and may receive a fastinformation table from an internet network through the IP communicationunit 130. It takes a predetermined time that the broadcast receptiondevice 100 tunes a specific frequency to receive a broadcast signal andanalyzes and processes the received broadcast signal. Additionally, whena broadcast signal is not received, it may be difficult for thebroadcast reception device 100 to scan a broadcast service forcorresponding frequency. Accordingly, when a fast information table isreceived from an internet network through the IP communication unit 130,the broadcast reception device 100 may efficiently perform a broadcastservice scan. Moreover, when a fast information table is received froman internet network through the IP communication unit 130, the broadcastreception device 100 may instantly perform a broadcast service scan.Additionally, as described above, the broadcast reception device 100 mayreceive a fast information table in an XML format through a broadcastnetwork. This will be described in more detail with reference to FIG.48.

FIG. 48 illustrates a syntax of a fast information table according toanother embodiment of the present invention.

The broadcast transmission device may transmit a fast information tablein an XML file format by using a section format and the broadcastreception device 100 may receive a fast information table in an XML fileformat.

At this point, a section including a fast information table may includeat least one of a table_id field, a section_syntax_indicator field, aprivate_indicator field, a section_length field, a table_id_extensionfield, a table_id_extension field, an FIT_data_version field, acurrent_next_indicator field, a section_number field, alast_section_number field, and a fit_byte( ) field.

The table_id field represents an identifier of a section including afast information table. At this point, the table_id may be 0xFA, thatis, one of reserved id values defined in ATSC A/65. According to aspecific embodiment of the present invention, the table_id field may bean 8-bit field.

The section_syntax_indicator field represents whether a fast informationtable is a private section table in the long formant of MEPG-2 TSstandard. According to a specific embodiment of the present invention,the section_syntax_indicator may be a 1-bit field.

The private_indicator field represents whether a current tablecorresponds to a private section. According to a specific embodiment ofthe present invention, the private_indicator may be a 1-bit field.

The section_length field represents the length of a section includedfollowing the section_length field. According to a specific embodimentof the present invention, the section_length field may be a 12-bitfield.

The table_id_extension field represents an identifier identifying fastinformation. According to a specific embodiment of the presentinvention, the table_id_extension field may be a 16-bit field.

The FIT_data_version field represents version information on the syntaxand semantics of a fast information table. The broadcast receptiondevice 100 may determine whether to process a corresponding fastinformation table by using the FIT_data_version field. For example, whena value of the FIT_data_version field represents a version that thebroadcast reception device 100 does not support, the broadcast receptiondevice 100 may not process a fast information table. According to aspecific embodiment of the present invention, the FIT_data_version fieldmay be a 5-bit field.

The current_next_indicator field represents whether information of afast information table is currently available. In more detail, when avalue of the current_next_indicator field is 1, thecurrent_next_indicator field may represent that information of a fastinformation table is available. Moreover, when a value of thecurrent_next_indicator field is 1, information of a fast informationtable is available for the next time. According to a specific embodimentof the present invention, the current_next_indicator field may be a1-bit field.

The section_number field represents a current section number. Accordingto a specific embodiment of the present invention, the section_numberfield may be an 8-bit field.

The last_section_number field represents the last section number. Whenthe size of a fast information table is large, the fast informationtable may be divided into a plurality of sections and then transmitted.At this point, the broadcast reception device 100 determines whether allsections necessary for a fast information table are received on thebasis of the section_number field and the last_section_number field.According to a specific embodiment of the present invention, thelast_section_number field may be an 8-bit field.

The fit_byte( ) field includes a fast information table in an XMLformat. According to a specific embodiment of the present invention, thefit_byte( ) field may include a fast information table in a compressedXML format.

According to an embodiment of the present invention, provided are abroadcast transmission device, an operation method thereof, a broadcastreception device, and an operation method thereof for efficientbroadcast service scan.

According to an embodiment of the present invention, provided are abroadcast transmission device, an operation method thereof, a broadcastreception device, and an operation method thereof for instantacquisition of broadcast service connection information.

FIG. 49 is a diagram illustrating configuration of ROHC_init_descriptor() according to an embodiment of the present invention.

Robust header compression (RoHC) according to an embodiment of thepresent invention may be configured for a bidirectional transmissionsystem. In the bidirectional transmission system, a RoHC compressor anda RoHC decompressor according to an embodiment of the present inventionmay perform an initial set up procedure and in this procedure, transmitand receive a parameter required for the initial procedure. According toan embodiment of the present invention, the procedure for transmittingand receiving the parameter required for aforementioned initialprocedure can be referred as a negotiation procedure or aninitialization procedure. However, according to an embodiment of thepresent invention, a unidirectional system such as a broadcast systemcannot perform the aforementioned negotiation procedure and can replacethe aforementioned initialization procedure with a separate method.

According to an embodiment of the present invention, during theinitialization procedure, the RoHC compressor and the RoHC decompressormay transmit and receive the following parameters. The parameterrequired for the initial procedure according to an embodiment of thepresent invention may include MAX_CID, LARGE_CIDS, PROFILES,FEEDBACK_FOR, and/or MRRU.

MAX_CID may be used to notify the decompressor of a maximum value of acontext ID (CID).

LARGE_CIDS may indicate whether a short CID (0 to 15 (decimal number))and an embedded CID (0 to 16383 (decimal number)) are used forconfiguration of the CID. Thus, a size of a byte for representation ofthe CID may also be determined.

PROFILES may indicate a range of a protocol for header compression viaRoHC. According to an embodiment of the present invention, RoHC cancompress and restore a stream when the compressor and the decompressorhave the same profile.

FEEDBACK_FOR may correspond to an optionally used field and indicatewhether a backward channel for transmission of feedback information ispresent in a corresponding RoHC channel.

A maximum reconstructed reception unit (MRRU) may indicate a maximumsize of a segment when segmentation is used in the RoHC compressor.

According to an embodiment of the present invention, a descriptorincluding parameters may be transmitted in order to transmit a parameterrequired for the aforementioned RoHC initial procedure.

According to an embodiment of the present invention,ROHC_init_descriptor( ) may include a descriptor_tag field, adescriptor_length field, a context_id field, a context_profile field, amax_cid field, and/or a large_cid field.

The descriptor_tag field may identify whether the descriptor is adescriptor including a parameter required for a RoHC initial procedure.

The descriptor_length field may indicate a length of the descriptor.

The context_id field may indicate a CID of a corresponding RoHC packetstream.

The context_profile field may be a field including the aforementionedPROFILES parameter and indicate a range of a protocol for headercompression via RoHC.

The max_cid field may be a field including the aforementioned MAX_CIDparameter and may indicate a maximum value of a CID.

The large_cid field may be a field including the aforementionedLARGE_CIDS parameter and may indicate whether a short CID (0 to 15(decimal number)) and an embedded CID (0 to 16383 (decimal number)) areused for configuration of the CID.

According to an embodiment of the present invention,ROHC_init_descriptor( ) may include the aforementioned FEEDBACK_FORparameter and/or MRRU parameter.

FIG. 50 is a diagram illustrating configuration ofFast_Information_Chunk( ) including ROHC_init_descriptor( ) according toan embodiment of the present invention.

ROHC_init_descriptor( ) according to an embodiment of the presentinvention may be transmitted through a fast information channel (FIC).In this case, ROHC_init_descriptor( ) may be included inFast_Information_Chunk( ) and transmitted. According to an embodiment ofthe present invention, ROHC_init_descriptor( ) may be included in aservice level of Fast_Information_Chunk( ) and transmitted.

A field included in Fast_Information_Chunk( ) includingROHC_init_descriptor( ) according to an embodiment of the presentinvention has been described above.

ROHC_init_descriptor( ) according to an embodiment of the presentinvention may be changed in its term according to system configurationand changed in its size according to a system optimization situation.

Fast_Information_Chunk( ) according to an embodiment of the presentinvention may be referred to as fast information chunk.

FIG. 51 is a diagram illustrating configuration ofFast_Information_Chunk( ) including a parameter required for a RoHCinitial procedure according to an embodiment of the present invention.

The parameter required for the RoHC initial procedure according to anembodiment of the present invention may be transmitted through a fastinformation channel (FIC). In this case, the parameter required for theRoHC initial procedure may be included in Fast_Information_Chunk( ) andtransmitted. According to an embodiment of the present invention, theparameter required for the RoHC initial procedure may be included in aservice level of Fast_Information_Chunk( ) and transmitted.

A field included in Fast_Information_Chunk( ) including the parameterrequired for the RoHC initial procedure according to an embodiment ofthe present invention has been described above.

The parameter required for the RoHC initial procedure according to anembodiment of the present invention may be changed in its term accordingto system configuration and changed in its size according to a systemoptimization situation.

FIG. 52 is a diagram illustrating configuration ofFast_Information_Chunk( ) including ROHC_init_descriptor( ) according toanother embodiment of the present invention.

According to an embodiment of the present invention, when importantinformation about a component included in a broadcast service isincluded in Fast_Information_Chunk( ) and transmitted,ROHC_init_descriptor( ) may be included in a component level ofFast_Information_Chunk( ) and transmitted. That is,ROHC_init_descriptor( ) may be transmitted for each respective componentincluded in Fast_Information_Chunk( ).

A field included in Fast_Information_Chunk( ) includingROHC_init_descriptor( ) according to another embodiment of the presentinvention has been described above.

ROHC_init_descriptor( ) according to an embodiment of the presentinvention may be changed in its term according to system configurationand changed in its size according to a system optimization situation.

FIG. 53 is a diagram illustrating configuration ofFast_Information_Chunk( ) including a parameter required for a RoHCinitial procedure according to another embodiment of the presentinvention.

According to an embodiment of the present invention, when importantinformation about a component included in a broadcast service isincluded in Fast_Information_Chunk( ) and transmitted, a parameterrequired for the RoHC initial procedure may be included in a componentlevel of Fast_Information_Chunk( ) and transmitted. That is, theparameter required for the RoHC initial procedure may be transmitted oreach respective component included in Fast_Information_Chunk( ).

A field included in Fast_Information_Chunk( ) including a parameterrequired for the RoHC initial procedure according to another embodimentof the present invention has been described above.

The parameter required for the RoHC initial procedure according to anembodiment of the present invention may be changed in its term accordingto system configuration and changed in its size according to a systemoptimization situation.

FIG. 54 is a flowchart of a method for transmitting a broadcast signalaccording to an embodiment of the present invention.

A transmitter according to an embodiment of the present invention maytransmit a broadcast signal through the following procedure. First, thetransmitter according to an embodiment of the present invention mayencode broadcast data (SL54010). Then the transmitter according to anembodiment of the present invention may generate a packet including theencoded broadcast data (SL54020). Here, the transmitter according to anembodiment of the present invention may add an RTP header, a UDP header,and an IP header to the broadcast data to generate an IP/UDP/RTP packet.According to an embodiment of the present invention, when transmissionis not performed in real time, a FLUTE header, etc. may be added insteadof the aforementioned RTP header. Then the transmitter according to anembodiment of the present invention may apply robust header compression(RoHC) on a header of the packet generated in the previous procedure togenerate a RoHC packet (SL54030). Then the transmitter according to anembodiment of the present invention may generate fast informationincluding configuration information of a broadcast stream and broadcastservice related information and transmit the fast information through afirst channel (SL54040). The fast information according to an embodimentof the present invention may refer to fast information. According to anembodiment of the present invention, the fast information may beincluded in fast information chunk and transmitted. The first channelaccording to an embodiment of the present invention may refer to a fastinformation channel (FIC). A detailed description thereof has been givenwith reference to FIGS. 34, 37, 38, 39, and 40. Then the transmitteraccording to an embodiment of the present invention may transmit thebroadcast stream including the RoHC packet generated in the previousprocedure through a second channel (SL54050). The second channelaccording to an embodiment of the present invention may refer to PLP orDP. The broadcast data according to an embodiment of the presentinvention may include video data, audio data, additional data, etc. Adetailed description thereof has been given with reference to FIGS. 31to 33.

According to another embodiment of the present invention, fastinformation may include RoHC initialization information forinitialization of information about robust header compression. Accordingto an embodiment of the present invention, information included in aRoHC header may be initialized for each unit of context including one ormore RoHC packets. The RoHC initialization information according to anembodiment of the present invention may refer to information used in theaforementioned initialization procedure. The RoHC initializationinformation according to an embodiment of the present invention mayrefer to information included in ROHC_init_descriptor( ) which has beendescribed with reference to FIG. 49.

According to another embodiment of the present invention, the RoHCinitialization information may include context identificationinformation for identification of context indicating one or more RoHCpacket units, context profile information indicating a range of aprotocol for header compression of a RoHC packet, maximum contextidentification information indicating a maximum value of the contextidentification information, and/or large context identificationinformation indicating representation format of the contextidentification information. According to an embodiment of the presentinvention, the context identification information may refer tocontext_id, the context profile information may refer tocontext_profile, the maximum context identification information mayrefer to max_cid, and the large context identification information mayrefer to large_cid, which has been described with reference to FIG. 49.

According to another embodiment of the present invention, the RoHCinitialization information may include feedback channel informationindicating whether a backward channel for transmission of feedbackinformation is present in a channel for transmission of a RoHC packetand/or maximum segment size information indicating a maximum size of onesegment when a RoHC packet is segmented to one or more segments.According to an embodiment of the present invention, the feedbackchannel information may refer to FEEDBACK_FOR and the maximum segmentsize information may refer to a maximum reconstructed reception unit(MRRU), which has been described with reference to FIG. 49.

According to another embodiment of the present invention, the RoHCinitialization information may be included in a service level in fastinformation. The fast information according to an embodiment of thepresent invention may include broadcast service related information andinclude a service ID for identification of a broadcast service. The RoHCinitialization information according to an embodiment of the presentinvention may be included in a service level identified by the serviceID, which has been described with reference to FIGS. 50 and 51.

According to another embodiment of the present invention, the fastinformation may further include component related information includedin a broadcast service and the RoHC initialization information may beincluded in a component level in the fast information. The fastinformation according to an embodiment of the present invention mayinclude information about one or more components included in one serviceand include a component ID for identification of a component. The RoHCinitialization information according to an embodiment of the presentinvention may be included in a component level identified by thecomponent ID, which has been described with reference to FIGS. 52 and53.

According to another embodiment of the present invention, the RoHCinitialization information may be included in a descriptor. A descriptorincluding the RoHC initialization information according to an embodimentof the present invention may refer to ROHC_init_descriptor( ). Adescriptor including the RoHC initialization information according to anembodiment of the present invention may be included in a component levelor service level of fast information, which has been described withreference to FIGS. 50 and 52.

FIG. 55 is a flowchart of a method for receiving a broadcast signalaccording to an embodiment of the present invention.

A receiver according to an embodiment of the present invention mayreceive a broadcast signal through the following procedure. First, thereceiver according to an embodiment of the present invention may receivefast information including configuration information of a broadcaststream and broadcast service related information through a first channel(SL55010), which has been described with reference to FIGS. 34, 37, 38,39, and 40. Then the receiver according to an embodiment of the presentinvention may receive the broadcast stream including a RoHC packet onwhich robust header compression (RoHC) is performed, through a secondchannel (SL55020), which has been described with reference to FIGS. 31to 33. Then the receiver may extract a RoHC packet from the broadcaststream received in the previous procedure using the fast informationreceived in the previous procedure and decompress the extracted RoHCpacket to generate an IP packet (SL55030). According to an embodiment ofthe present invention, the receiver may extract a RoHC packet includinga desired service or component based on the service or component relatedinformation included in the fast information. The receiver according toan embodiment of the present invention may decompress the compressedheader of the RoHC packet. Then the receiver may extract broadcast datafrom the IP packet generated in the previous procedure (SL55040). Thenthe receiver may decode the extracted broadcast data (SL55050).

According to another embodiment of the present invention, the fastinformation may include RoHC initialization information forinitialization of information about robust header compression. Accordingto an embodiment of the present invention, information included in aRoHC header may be initialized for each unit of context including one ormore RoHC packets. The RoHC initialization information according anembodiment of the present invention may refer to information used in theaforementioned initialization procedure. The RoHC initializationinformation according to an embodiment of the present invention mayrefer to information included in ROHC_init_descriptor( ) which has beendescribed with reference to FIG. 49.

According to another embodiment of the present invention, RoHCinitialization information may include context identificationinformation for identification of context indicating one or more RoHCpacket units, context profile information indicating a range of aprotocol of compression of an RoHC packet, maximum contextidentification information indicating a maximum value of the contextidentification information, and/or large context identificationinformation indicating representation format of the contextidentification information. According to an embodiment of the presentinvention, the context identification information may refer tocontext_id, the context profile information may refer tocontext_profile, the maximum context identification information mayrefer to max_cid, and the large context identification information mayrefer to large_cid, which has been described with reference to FIG. 49.

According to another embodiment of the present invention, RoHCinitialization information may include feedback channel informationwhether a backward channel for transmission of feedback information ispresent in a channel for transmission of a RoHC packet and/or maximumsegment size information indicating a maximum size of one segment when aRoHC packet is segmented to one or more segments. According to anembodiment of the present invention, the feedback channel informationmay refer to FEEDBACK_FOR and the maximum segment size information mayrefer to a maximum reconstructed reception unit (MRRU), which has beendescribed with reference to FIG. 49.

According to another embodiment of the present invention, the RoHCinitialization information may be included in a service level in fastinformation. The fast information according to an embodiment of thepresent invention may include broadcast service related information andinclude a service ID for identification of a broadcast service. The RoHCinitialization information according to an embodiment of the presentinvention may be included in a service level identified by the serviceID, which has been described with reference to FIGS. 50 and 51.

According to another embodiment of the present invention, the fastinformation may further include component related information includedin a broadcast service and the RoHC initialization information may beincluded in a component level in the fast information. The fastinformation according to an embodiment of the present invention mayinclude information about one or more components included in one serviceand include a component ID for identification of a component. The RoHCinitialization information according to an embodiment of the presentinvention may be included in a component level identified by thecomponent ID, which has been described with reference to FIGS. 52 and53.

According to another embodiment of the present invention, the RoHCinitialization information may be included in a descriptor. A descriptorincluding the RoHC initialization information according to an embodimentof the present invention may refer to ROHC_init_descriptor( ). Adescriptor including the RoHC initialization information according to anembodiment of the present invention may be included in a component levelor service level of fast information, which has been described withreference to FIGS. 50 and 52.

FIG. 56 is a diagram illustrating configuration of a broadcast signaltransmitting apparatus L56060 according to an embodiment of the presentinvention.

The transmitting apparatus L56060 according to an embodiment of thepresent invention may include an encoder L56010, a packet generatorL56020, a RoHC compressor L56030, a first transmitter L56040, and/or asecond transmitter L56050.

Components included in the transmitting apparatus according to anembodiment of the present invention may perform the respectivecorresponding procedures of the aforementioned method for transmitting abroadcast signal according to an embodiment of the present invention.

The encoder L56010 may encode broadcast data.

The packet generator L56020 may generate a packet including the encodedbroadcast data.

The RoHC compressor L56030 may perform robust header compression (RoHC)on a header of the generated packet to generate a RoHC packet.

The first transmitter L56040 may generate fast information includingconfiguration information of a broadcast stream and broadcast servicerelated information and transmit the fast information through a firstchannel, which has been described with reference to FIGS. 34, 37, 38,39, and 40.

The second transmitter L56050 may transmit a broadcast stream includingthe generated RoHC packet through a second channel, which has beendescribed with reference to FIGS. 31 to 33.

FIG. 57 is a diagram illustrating configuration of a broadcast signalreceiving apparatus L57060 according to an embodiment of the presentinvention.

The receiving apparatus L57060 according to an embodiment of the presentinvention may include a first receiver L57010, a second receiver L57020,a RoHC decompressor L57030, an extractor L57040, and/or a decoderL57050.

Components included in the receiving apparatus according to anembodiment of the present invention may perform the respectivecorresponding procedures of the aforementioned method for receiving abroadcast signal according to an embodiment of the present invention.

The first receiver L57010 may receive fast information includingconfiguration information of a broadcast stream and broadcast servicerelated information through a first channel, which has been describedwith reference to FIGS. 34, 37, 38, 39, and 40. The first receiverL57010 according to an embodiment of the present invention may beincluded in the aforementioned broadcast receiver 110.

The second receiver L57020 may receive a broadcast stream including aRoHC packet on which robust header compression (RoHC) is performed,through a second channel, which has been described with reference toFIGS. 31 to 33. The second receiver L57020 according to an embodiment ofthe present invention may be included in the aforementioned broadcastreceiver 110.

The RoHC decompressor L57030 may extract a RoHC packet from the receivedbroadcast stream using fast information and decompress the extractedRoHC packet to generate an IP packet.

The extractor L57040 may extract broadcast data from the generated IPpacket.

The decoder L57050 may decode the extracted broadcast data.

The above-described steps can be omitted or replaced by steps executingsimilar or identical functions according to design.

Although the description of the present invention is explained withreference to each of the accompanying drawings for clarity, it ispossible to design new embodiment(s) by merging the embodiments shown inthe accompanying drawings with each other. And, if a recording mediumreadable by a computer, in which programs for executing the embodimentsmentioned in the foregoing description are recorded, is designed innecessity of those skilled in the art, it may belong to the scope of theappended claims and their equivalents.

An apparatus and method according to the present invention may benon-limited by the configurations and methods of the embodimentsmentioned in the foregoing description. And, the embodiments mentionedin the foregoing description can be configured in a manner of beingselectively combined with one another entirely or in part to enablevarious modifications.

In addition, a method according to the present invention can beimplemented with processor-readable codes in a processor-readablerecording medium provided to a network device. The processor-readablemedium may include all kinds of recording devices capable of storingdata readable by a processor. The processor-readable medium may includeone of ROM, RAM, CD-ROM, magnetic tapes, floppy discs, optical datastorage devices, and the like for example and also include such acarrier-wave type implementation as a transmission via Internet.Furthermore, as the processor-readable recording medium is distributedto a computer system connected via network, processor-readable codes canbe saved and executed according to a distributive system.

It will be appreciated by those skilled in the art that variousmodifications and variations can be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

Both apparatus and method inventions are mentioned in this specificationand descriptions of both of the apparatus and method inventions may becomplementarily applicable to each other.

Various embodiments have been described in the best mode for carryingout the invention.

The present invention is available in a series of broadcast signalprovision fields.

It will be apparent to those skilled in the art that variousmodifications and variations can be made in the present inventionwithout departing from the spirit or scope of the inventions. Thus, itis intended that the present invention covers the modifications andvariations of this invention provided they come within the scope of theappended claims and their equivalents.

What is claimed is:
 1. A method for transmitting a broadcast signal, themethod comprising: generating a packet carrying a broadcast service andservice signaling information, and a packet carrying fast informationfor supporting rapid service scans and service acquisition, the fastinformation including identification information for identifying thebroadcast service, service category information representing a categoryof the broadcast service and hidden information representing whether ornot the broadcast service is related to a test service; generating arobust header compression (RoHC) packet by compressing a header of eachpacket, and signaling information including context informationgenerated from the compressing the header of each packet; andtransmitting a signal frame including the RoHC packet and the signalinginformation, the signaling information is transmitted separately fromthe RoHC packet, the signaling information including: contextidentification information for representing a context identification(ID) for the RoHC packet, context profile information for a range whichis used for compressing a packet stream including the packets, maximumcontext identification information indicating a maximum value of thecontext ID, and configuration information for a configuration for thecontext information.
 2. The method of claim 1, wherein the signalinginformation includes large context identification information indicatinga representation format of the context identification information. 3.The method of claim 2, wherein the signaling information includes atleast one of feedback channel information indicating whether a backwardchannel for transmission of feedback information is present in a channelfor transmission of the RoHC packet and maximum segment size informationindicating a maximum size of one segment when the RoHC packet issegmented to one or more segments.
 4. The method of claim 1, wherein thesignaling information includes type information indicating a type ofsignaling carried in the signaling information.
 5. The method of claim1, wherein the fast information further includes information indicatingwhether one or more components of the broadcast service are protected,and information identifying a broadcast stream including the broadcastservice.
 6. A method for receiving a broadcast signal, the methodcomprising: receiving a signal frame including a robust headercompression (RoHC) packet and signaling information including contextinformation generated by compressing a header of each packet, thesignaling information is carried separately from the RoHC packet,wherein the RoHC packet is generated by compressing the header of eachpacket, a packet carrying a broadcast service and service signalinginformation for the broadcast service, and a packet carrying fastinformation for supporting rapid service scans and service acquisition,the fast information including identification information foridentifying the broadcast service, service category informationrepresenting a category of the broadcast service and hidden informationrepresenting whether or not the broadcast service is related to a testservice, and the signaling information including context identificationinformation for representing a context identification (ID) for the RoHCpacket, context profile information for a range which is used forcompressing a packet stream including the packets, maximum contextidentification information indicating a maximum value of the context ID,and configuration information for a configuration for the contextinformation; decompressing the RoHC packet to restore the IP packetstream based on the signaling information; parsing the fast informationin the packet; parsing the service signaling information in the packet;and decoding the broadcast service in the packet.
 7. The method of claim6, wherein the signaling information includes large contextidentification information indicating a representation format of thecontext identification information.
 8. The method of claim 7, whereinthe signaling information includes at least one of feedback channelinformation indicating whether a backward channel for transmission offeedback information is present in a channel for transmission of theRoHC packet and maximum segment size information indicating a maximumsize of one segment when the RoHC packet is segmented to one or moresegments.
 9. The method of claim 6, wherein the signaling informationincludes type information indicating a type of signaling carried in thesignaling information.
 10. The method of claim 6, wherein the fastinformation further includes information indicating whether one or morecomponents of the broadcast service are protected, and informationidentifying a broadcast stream including the broadcast service.
 11. Anapparatus for transmitting a broadcast signal, the apparatus comprising:a packet generator configured to generate a packet carrying a broadcastservice and service signaling information, and a packet carrying fastinformation for supporting rapid service scans and service acquisition,the fast information including identification information foridentifying the broadcast service, service category informationrepresenting a category of the broadcast service and hidden informationrepresenting whether or not the broadcast service is related to a testservice; a robust header compression (RoHC) compressor configured togenerate a robust header compression (RoHC) packet by compressing aheader of each packet, and signaling information including contextinformation generated from the compressing the header of each packet; atransmitter configured to transmit a signal frame including the RoHCpacket and the signaling information, the signaling information istransmitted separately from the RoHC packet, the signaling informationincluding context identification information for representing a contextidentification (ID) for the RoHC packet, context profile information fora range which is used for compressing a packet stream including thepackets, and maximum context identification information indicating amaximum value of the context ID, and configuration information for aconfiguration for the context information.
 12. An apparatus forreceiving a broadcast signal, the apparatus comprising: a receiverconfigured to receive a signal frame including a robust headercompression (RoHC) packet and signaling information including contextinformation generated by compressing a header of each packet thesignaling information is carried separately from the RoHC packet,wherein the RoHC packet is generated by compressing the header of eachpacket, a packet carrying a broadcast service and service signalinginformation for the broadcast service, and a packet carrying fastinformation for supporting rapid service scans and service acquisition,the fast information including identification information foridentifying the broadcast service, service category informationrepresenting a category of the broadcast service and hidden informationrepresenting whether or not the broadcast service is related to a testservice, and the signaling information including context identificationinformation for indicating a context identification (ID) for the RoHCpacket, context profile information for a range which is used forcompressing a packet stream including the packets, maximum contextidentification information indicating a maximum value of the context ID,and configuration information for a configuration for the contextinformation; a RoHC decompressor configured to decompress the RoHCpacket stream to restore the IP packet stream based on the signalinginformation; a signaling parser configured to parse the fast informationin the packet, wherein the signaling parser further parses the servicesignaling information in the packet; and a decoder configured to decodethe broadcast service in the packet.